CVE-2024-11483VulnerabilityPublished 25 Nov 2024Updated 20 Nov 2025

CVE-2024-11483: Improper Access Control

Source CVE Database V5

Not known to be exploited · CVSS 5.0 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

5.0Medium

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

EPSS: 0.5% chance of exploitation in 30 days – higher than 44% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Changed
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: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
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 25 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 2026-10-25.

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-11483, organizations should implement the following specific measures: 1) Monitor and audit OAuth2 token usage to detect anomalous privilege escalations or unexpected write operations originating from read-scoped tokens. 2) Enforce strict token scope validation and review OAuth2 provider configurations to ensure proper separation of read and write permissions. 3) Limit the issuance of OAuth2 tokens to the minimum necessary scope and duration, applying the principle of least privilege rigorously. 4) Apply network segmentation and access controls to restrict API endpoint exposure to trusted users and systems only. 5) Stay informed about vendor patches or updates addressing this vulnerability and prioritize timely deployment once available. 6) Conduct regular security assessments and penetration testing focused on API authentication and authorization mechanisms to identify similar weaknesses. 7) Implement multi-factor authentication and robust credential management to reduce the risk of token compromise. These targeted actions go beyond generic advice by focusing on OAuth2 token management and API access control hardening specific to AAP environments.

Description

A vulnerability was found in the Ansible Automation Platform (AAP). This flaw allows attackers to escalate privileges by improperly leveraging read-scoped OAuth2 tokens to gain write access. This issue affects API endpoints that rely on ansible_base.oauth2_provider for OAuth2 authentication. While the impact is limited to actions within the user’s assigned permissions, it undermines scoped access controls, potentially allowing unintended modifications in the application and consuming services.

Impact

The primary impact of CVE-2024-11483 is the potential for unauthorized modification of resources within the Ansible Automation Platform environment. Although the attacker cannot exceed the permissions assigned to the compromised user, the ability to escalate from read-only to write access can lead to unintended changes in automation workflows, configurations, or service consumption. This can disrupt operational processes, introduce misconfigurations, or enable further lateral movement within the environment. Organizations relying heavily on AAP for critical infrastructure automation may face increased risk of integrity violations and operational downtime. The vulnerability does not directly impact confidentiality or availability but compromises the integrity of managed resources. Given the widespread adoption of Ansible Automation Platform in enterprise IT environments, the vulnerability could affect organizations globally, especially those with complex automation pipelines and multi-tenant deployments where scoped access controls are essential for security.

References

Community reviews

Loading reviews…