dbcve.org
Aura Communication ManagerApplication · Avaya

CVE-2018-15611

MEDIUM · 6.7 CVSS v3.0 Published 2018-09-27
Fix available
A fix is available. Upgrade to 7.1.3.1 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 in the local system administration component of Avaya Aura Communication Manager can allow an authenticated, privileged user on the local system to gain root privileges. Affected versions include 6.3.x and all 7.x version prior to 7.1.3.1.

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 · high confidence

Local privilege escalation vulnerability in Avaya Aura Communication Manager's local system administration component allows an authenticated, privileged local user to gain root privileges. The flaw exists in versions 6.3.x and 7.x prior to 7.1.3.1.

MitigationUpgrade Avaya Aura Communication Manager to version 7.1.3.1 or later to remediate this vulnerability.

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 Communication ManagerApplication
Affected:>= 6.3.0.1, <= 6.3.17.0>= 7.0, < 7.1.3.1

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.0/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 Avaya Aura Communication Manager version
    Access the system administration interface or check system files/CLI for the installed Communication Manager version (typically via 'show version' or 'system management' interface)
    Affected if Version is 6.3.0.1 through 6.3.17.0, or 7.0.x through 7.1.3.0 (versions below 7.1.3.1)
  2. Confirm local administration access is enabled
    Verify the local system administration component/service is accessible on the Avaya Aura system (check if local admin interface or CLI is available for privileged users)
    Affected if Local system administration component is enabled and accessible on the system
  3. Verify user privilege level
    Confirm the user has authenticated, privileged local access (e.g., 'admin' or equivalent privileged account with system administration rights)
    Affected if User has authenticated, privileged local user credentials for the Communication Manager administration interface

System is affected if Avaya Aura Communication Manager version is 6.3.0.1-6.3.17.0 or 7.0-7.1.3.0 AND the local system administration component is enabled with authenticated privileged local user 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.

From vendor data
Upgrade available Upgrade to 7.1.3.1 or later
Fixed in 7.1.3.1
Interim mitigation

Upgrade Avaya Aura Communication Manager to version 7.1.3.1 or later to remediate this vulnerability.

Fix this in Aura Communication Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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