dbcve.org
Communication ManagerApplication · Avaya

CVE-2008-6710

HIGH · 9.0 CVSS v2.0 Published 2009-04-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
96/100
Remediation priority · Urgent
Remotely reachable 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
Unspecified vulnerability in the Web administration interface in Avaya Communication Manager 3.1.x before CM 3.1.4 SP2 and 4.0.x before 4.0.3 SP1 allows remote authenticated administrators to gain root privileges via unknown vectors related to "configuring data viewing or restoring credentials."

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

Avaya Communication Manager versions 3.1.x before 3.1.4 SP2 and 4.0.x before 4.0.3 SP1 contain a privilege escalation vulnerability in the web administration interface. Authenticated administrators can exploit unspecified vectors related to data viewing configuration or credential restoration to gain root-level system access.

MitigationUpgrade Avaya Communication Manager to version 3.1.4 SP2 or later, or 4.0.3 SP1 or later. If immediate patching is not feasible, restrict administrative web interface access to a minimal set of trusted users and implement network segmentation to limit exposure.

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
Communication ManagerApplication
Affected:= 3.1= 3.1.1= 3.1.2= 3.1.3= 4.0= 4.0.1= 4.0.2= 4.0.3

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
Network
Complexity
Low
Authentication
Single
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:S/C:C/I:C/A:C

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 Avaya Communication Manager version
    Access the system admin interface or use the command line interface (CLI) to query the software version. On the system, run: 'swversion' or check the system information screen in the administration portal.
    Affected if The displayed version matches 3.1, 3.1.1, 3.1.2, 3.1.3, 4.0, 4.0.1, 4.0.2, or 4.0.3, or falls within 3.1.x before 3.1.4 SP2, or 4.0.x before 4.0.3 SP1.
  2. Confirm web administration interface is accessible
    Verify that the HTTP/HTTPS web administration interface is enabled and reachable on the Avaya Communication Manager server. Check the service status or attempt to access the admin login page.
    Affected if The web administration interface is active and accepts authentication requests.
  3. Verify administrator account existence
    Check for existing administrator accounts in the system. In the web admin interface, navigate to User Administration or use CLI commands to list admin-level accounts.
    Affected if One or more administrator-level accounts exist with privileges to access the web administration interface.
  4. Check for data viewing configuration or credential restoration features
    Within the web administration interface, examine the configuration menus for data viewing options or credential restoration/password reset functions. These are the reported exploitation vectors.
    Affected if The data viewing configuration or credential restoration features are present and accessible to authenticated administrators.

The environment is affected if Avaya Communication Manager is running a version between 3.1 and 3.1.3, or between 4.0 and 4.0.3, and the web administration interface with administrator accounts is accessible.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Avaya Communication Manager to version 3.1.4 SP2 or later, or 4.0.3 SP1 or later. If immediate patching is not feasible, restrict administrative web interface access to a minimal set of trusted users and implement network segmentation to limit exposure.

Recommended fix Moderate confidence

CM 3.1.4 SP2 (or later in the 3.1.x branch)

  1. Download CM 3.1.4 SP2 or later from the Avaya support portal (support.avaya.com)
  2. Review Avaya upgrade documentation and release notes for Communication Manager 3.1.x
  3. Schedule a maintenance window as upgrades require system downtime
  4. Backup current configuration and all critical data
  5. Apply the upgrade following Avaya's official upgrade procedure for Communication Manager
  6. Verify the upgrade was successful by logging into the web administration interface
  7. Confirm the version number reflects CM 3.1.4 SP2 or higher
  8. Test that the web administration interface functions correctly after upgrade
Caveat Review release notes for any configuration or feature changes between 3.1.x and 3.1.4 SP2; some legacy features may be deprecated

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

Fix this in Communication Manager Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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