CVE-2024-7480VulnerabilityPublished 8 Aug 2024Updated 1 Oct 2025

CVE-2024-7480: Avaya Aura System Manager · CWE-266

Affects Avaya Aura System ManagerSource CVE Database V5

Not known to be exploited · CVSS 4.2 Medium.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

4.2Medium

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

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

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

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

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

Attack Vector: Local: The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or remotely (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., tricking a legitimate user into opening a malicious document).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
User Interaction: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
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: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within 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 8 Aug 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-26.

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 this vulnerability effectively, European organizations should: 1) Restrict administrative CLI access strictly to trusted personnel and enforce the principle of least privilege to minimize the number of users with such access. 2) Implement robust multi-factor authentication (MFA) for all administrative accounts to reduce the risk of credential compromise. 3) Monitor and audit CLI access logs continuously to detect any unusual or unauthorized file access attempts promptly. 4) Segregate management networks to isolate Avaya Aura System Manager from general user networks, limiting exposure. 5) Apply network-level controls such as IP whitelisting and VPN requirements for accessing the management interface. 6) Stay alert for vendor updates or patches addressing this vulnerability and plan for timely deployment once available. 7) Conduct internal security awareness training focusing on the risks of privileged access misuse. 8) Consider deploying file integrity monitoring solutions to detect unauthorized file access or exfiltration activities. These measures go beyond generic advice by focusing on access control hardening, monitoring, and network segmentation tailored to the specific nature of this vulnerability.

Description

An Improper access control vulnerability was found in Avaya Aura System Manager which could allow a command-line interface (CLI) user with administrative privileges to read arbitrary files on the system. Affected versions include 10.1.x.x and 10.2.x.x. Versions prior to 10.1 are end of manufacturer support.

Impact

For European organizations using Avaya Aura System Manager, this vulnerability poses a moderate confidentiality risk. Since the flaw allows arbitrary file reading by administrative CLI users, sensitive data such as configuration files, credentials, or internal documentation could be exposed. This could lead to further compromise if attackers use the leaked information to escalate privileges or move laterally within the network. The impact is heightened in sectors with strict data protection regulations such as GDPR, where unauthorized data disclosure can result in regulatory penalties and reputational damage. Organizations in telecommunications, finance, healthcare, and government sectors that rely on Avaya Aura System Manager for unified communications and system management are particularly at risk. However, the requirement for administrative CLI access limits the attack surface to insiders or attackers who have already breached initial defenses, reducing the likelihood of remote exploitation. Still, the vulnerability underscores the importance of strict access controls and monitoring of privileged accounts.

CWE-266Incorrect Privilege Assignment (opens in a new tab)
Base weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
A product incorrectly assigns a privilege to a particular actor, creating an unintended sphere of control for that actor.
Architecture and Design · Operation
Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
Architecture and Design · Operation · Environment Hardening
Run your code using the lowest privileges that are required to accomplish the necessary tasks. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment.
OWASP Cheat Sheets
Docker Security (opens in a new tab)
Third Party Javascript Management (opens in a new tab)
Virtual Patching (opens in a new tab)
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V1.4.4 (opens in a new tab)
V1.4.5 (opens in a new tab)
V1.10.1 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

download.avaya.com/css/public/documents/101091159 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 4 Oct 2025, 10:32 UTC

WeaknessesCWE-266

Technical details

References

Community reviews

Related threats