dbcve.org
Aura Communication ManagerApplication · Avaya

CVE-2022-2249

MEDIUM · 6.7 CVSS v3.1 Developing Published 2022-10-12
Fix available
A fix is available. Upgrade to 8.1.3.4 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
Privilege escalation related vulnerabilities were discovered in Avaya Aura Communication Manager that may allow local administrative users to escalate their privileges. This issue affects Communication Manager versions 8.0.0.0 through 8.1.3.3 and 10.1.0.0.

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 · low confidence
Developing — this CVE was published recently and its authoritative NVD entry is still being established, so we're holding a technical summary until the source data settles rather than publish something unreliable. Re-checking after 2026-08-01.

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 Communication ManagerApplication
Affected:>= 8.0, < 8.1.3.4= 10.1.0.0

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

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.4 or later
Fixed in 8.1.3.4
Recommended fix Moderate confidence

8.1.3.4 or later for the 8.x product line; contact Avaya for 10.x line remediation

  1. 1. Identify the current installed version of Avaya Aura Communication Manager using the system administration interface or CLI.
  2. 2. If running version 8.0.0.0 through 8.1.3.3, plan for upgrade to version 8.1.3.4 or later.
  3. 3. If running version 10.1.0.0, contact Avaya support for specific patch availability as no direct upgrade path is specified in the advisory.
  4. 4. Download the appropriate upgrade package from the Avaya support portal at download.avaya.com.
  5. 5. Review Avaya upgrade documentation and ensure backup of current configuration is completed.
  6. 6. Apply the upgrade during a planned maintenance window following Avaya's standard upgrade procedures.
  7. 7. Verify the upgrade was successful and test that privilege escalation vulnerability is remediated.
Caveat Review Avaya upgrade documentation for any compatibility or configuration changes required by the new version

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-2249 — 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-2249 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