dbcve.org
Aura Application Enablement ServicesApplication · Avaya

CVE-2022-2975

MEDIUM · 6.7 CVSS v3.1 Published 2022-10-06
Fix available
A fix is available. Upgrade to 8.1.3.5 / 10.1.0.2 or later.
See remediation →
69/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability related to weak permissions was detected in Avaya Aura Application Enablement Services web application, allowing an administrative user to modify accounts leading to execution of arbitrary code as the root user. This issue affects Application Enablement Services versions 8.0.0.0 through 8.1.3.4 and 10.1.0.0 through 10.1.0.1. Versions prior to 8.0.0.0 are end of manufacturing support and were not evaluated.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Weak permissions in Avaya Aura Application Enablement Services web application allow an authenticated administrative user to modify accounts in a way that leads to arbitrary code execution with root privileges. This represents a privilege escalation vulnerability where a user with administrative access can gain full system-level control.

MitigationUpgrade to a patched version of Application Enablement Services as provided by Avaya. In the interim, restrict administrative access to trusted personnel and monitor for suspicious account modifications.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Aura Application Enablement ServicesApplication
Affected:>= 8.0.0.0, < 8.1.3.5>= 10.1.0.0, < 10.1.0.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed version
    Locate and verify the version of Avaya Aura Application Enablement Services installed in your environment
    Affected if Version is 8.0.0.0 through 8.1.3.4, or 10.1.0.0 through 10.1.0.1 (falls within the vulnerable ranges)
  2. Confirm web application access
    Determine whether the Avaya Aura Application Enablement Services web management interface is accessible
    Affected if Web interface is exposed and reachable
  3. Audit administrative accounts
    Review all administrative user accounts configured in the web application for unauthorized modifications or unexpected accounts
    Affected if Unexpected administrative accounts exist or account configurations have been altered
  4. Inspect for root-level changes
    Examine the underlying system for unexpected root-privileged processes, scripts, or modified system files that may indicate code execution
    Affected if Unexpected root-privileged processes or modified system files are present

Environment is affected if the installed version falls within the vulnerable ranges AND the web application is accessible to authenticated administrators who could potentially modify accounts to gain root access

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 8.1.3.5 / 10.1.0.2 or later
Fixed in 8.1.3.510.1.0.2
Interim mitigation

Upgrade to a patched version of Application Enablement Services as provided by Avaya. In the interim, restrict administrative access to trusted personnel and monitor for suspicious account modifications.

Recommended fix High confidence

8.1.3.5 for 8.x releases; 10.1.0.2 for 10.x releases

  1. Identify the current installed version of Avaya Aura Application Enablement Services
  2. If running version 8.0.0.0 through 8.1.3.4, download and upgrade to version 8.1.3.5 from the Avaya download portal (download.avaya.com)
  3. If running version 10.1.0.0 through 10.1.0.1, download and upgrade to version 10.1.0.2 from the Avaya download portal (download.avaya.com)
  4. After upgrading, verify the new version is correctly installed
  5. Test that the privilege management controls properly restrict account modifications to prevent arbitrary code execution as root
Caveat Standard upgrade considerations apply - review Avaya upgrade documentation for prerequisites and migration steps

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Aura Application Enablement Services Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-2975 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-2975 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data