VulnerabilityPublished 4 Nov 2024Updated 6 Nov 2024

CVE-2024-45164: Incorrect Permissions

Source CVE Database V5

Not known to be exploited · CVSS 4.3 Medium · fixed in 19.2.0.20240814 : update affected systems when convenient.

Data as of 26 Oct 2026, 09:15 UTC

CVSS 3.1 base score

4.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 19.2.0.20240814, 19.2.0.3, 19.2.0

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: None
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 4 Nov 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

To mitigate CVE-2024-45164, organizations should promptly upgrade Akamai SIA ThreatAvert to version 19.2.0 or later and Apps Portal to version 19.2.0.3 or 19.2.0.20240814 or later, where the authorization controls have been corrected. If you cannot patch yet, restrict authenticated user access to the ThreatAvert Policy page by implementing strict role-based access controls (RBAC) and monitoring for unauthorized access attempts to the /#app/intelligence/threatAvertPolicies URI. Employ network segmentation and least privilege principles to limit the number of users with authenticated access to the management interfaces. Additionally, enable detailed logging and alerting on policy changes to detect any unauthorized disabling of policy enforcement. Conduct regular audits of user permissions and review access logs for suspicious activity. If patching is delayed, consider temporary compensating controls such as web application firewalls (WAF) rules to block direct access to the vulnerable URI for non-admin users. Finally, educate administrators and users about the risk and encourage vigilance against internal misuse.

Description

Akamai SIA (Secure Internet Access Enterprise) ThreatAvert, in SPS (Security and Personalization Services) before the latest 19.2.0 patch and Apps Portal before 19.2.0.3 or 19.2.0.20240814, has incorrect authorization controls for the Admin functionality on the ThreatAvert Policy page. An authenticated user can navigate directly to the /#app/intelligence/threatAvertPolicies URI and disable policy enforcement.

Impact

The primary impact of CVE-2024-45164 is the potential degradation of security policy integrity within organizations using Akamai SIA ThreatAvert. By allowing an authenticated user with limited privileges to disable policy enforcement, attackers or malicious insiders can bypass critical threat detection and mitigation controls. This can lead to increased exposure to threats that would otherwise be blocked or mitigated by ThreatAvert policies. Although confidentiality and availability are not directly affected, the weakening of security controls increases the risk of subsequent attacks or data breaches. Organizations relying heavily on Akamai SIA for threat enforcement, especially those with multiple users having authenticated access, face a risk of internal policy tampering. This could undermine compliance requirements and increase the likelihood of successful cyberattacks. The absence of known exploits reduces immediate risk but does not eliminate the threat, especially in environments with less stringent internal access controls.

CWE-732Incorrect Permission Assignment for Critical Resource (opens in a new tab)
Class weaknessLikelihood of exploit: HighOWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.
Implementation
When using a critical resource such as a configuration file, check to see if the resource has insecure permissions (such as being modifiable by any regular user), and generate an error or even exit the software if there is a possibility that the resource could have been modified by an unauthorized party.
Architecture and Design
Divide the software into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully defining distinct user groups, privileges, and/or roles. Map these against data, functionality, and the related resources. Then set the permissions accordingly.
Architecture and Design · Operation · Sandbox or Jail
Run the code in a "jail" or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which files can be accessed in a particular directory or which commands can be executed by the software.
OWASP Cheat Sheets
REST Assessment (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V4.3.3 (opens in a new tab)
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
Attack patterns
Accessing Functionality Not Properly Constrained by ACLs (opens in a new tab)
Directory Indexing (opens in a new tab)
Using Malicious Files (opens in a new tab)
Exploiting Incorrectly Configured Access Control Security Levels (opens in a new tab)
Signing Malicious Code (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 28 Feb 2026, 06:52 UTC

WeaknessesCWE-732

Technical details

References

Community reviews

Related threats