Security readout for executives and security teams
Plain-English summary
Avaya Aura Device Services versions 7.0 through 8.1.4.0 have a code execution flaw that may let a high-privileged local user run specially crafted scripts. This is not a broad internet worm risk from the provided evidence, but it matters for environments where Avaya systems are business-critical.
Executive priority
Treat this as a scheduled but real remediation item. Prioritize faster if Avaya Aura Device Services supports critical communications, has many administrators, or shares hosts with sensitive services.
Technical view
CVE-2021-25654 is described as arbitrary code execution in Avaya Aura Device Services. The CVSS 3.1 score is 6.2 with high attack complexity and high privileges required, and CWE-378 is assigned. The provided description says local user execution, while the CVSS vector lists network attack vector.
Likely exposure
Organizations running Avaya Aura Device Services 7.0 through 8.1.4.0 are potentially exposed. The bundle does not identify affected deployments beyond Avaya Aura Device Services, so do not generalize this to other Avaya products without vendor confirmation.
Exploitation context
The source bundle does not cite active exploitation, and KEV status is false. Exploitation appears constrained by high privileges and high complexity, but successful exploitation could affect confidentiality and integrity significantly on the affected system.
Researcher notes
The bundle has a notable wording mismatch: the description says local user, while CVSS lists AV:N and PR:H. Validate against Avaya advisory details before scoping detection or exposure assumptions. No public exploit evidence is provided here.
Mitigation direction
- Inventory Avaya Aura Device Services deployments and record exact versions.
- Review Avaya advisory 101076523 for vendor-supported remediation.
- Upgrade or apply fixes only as directed by Avaya guidance.
- Limit privileged/local access to Avaya Aura Device Services hosts.
- Monitor privileged script execution and administrative changes on affected systems.
Validation and detection
- Confirm whether any deployment runs versions 7.0 through 8.1.4.0.
- Check Avaya advisory 101076523 against installed build numbers.
- Verify privileged user access is limited to approved administrators.
- Review logs for unexpected script execution or administrative changes.
- Document compensating controls where immediate remediation is unavailable.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-378: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2021-25654 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.2 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:L
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:L0.75.5Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.2MediumVector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:L
Source materials
- CVE List V5 sourceCVE List V5
- https://support.avaya.com/css/P8/documents/101076523CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Creation of Temporary File With Insecure Permissions
Creation of Temporary File With Insecure Permissions represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.