dbcve.org
Communication ManagerApplication · Avaya

CVE-2008-6711

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 users to execute arbitrary commands via unknown vectors related to "viewing system logs."

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

Command injection vulnerability in Avaya Communication Manager's web administration interface allows authenticated remote users to execute arbitrary operating system commands through the system log viewing functionality. The vulnerability exists in versions 3.1.x before 3.1.4 SP2 and 4.0.x before 4.0.3 SP1.

MitigationUpgrade Avaya Communication Manager to version 3.1.4 SP2 or 4.0.3 SP1 or later. Until patched, restrict web administration interface access to trusted admin accounts only via network segmentation or VPN.

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= 3.1.4= 4.0= 4.0.1= 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 Avaya Communication Manager version
    Access the web administration interface or check system files for the installed version number. This is typically visible in the login page or in the system status/About section of the web interface.
    Affected if The version is 3.1, 3.1.1, 3.1.2, 3.1.3, 3.1.4, 4.0, 4.0.1, or 4.0.3 (versions before 3.1.4 SP2 or 4.0.3 SP1)
  2. Confirm web administration interface is enabled
    Verify that the web-based administration interface is accessible and active on the Avaya system. Check network listening services or consult system documentation for the web interface URL.
    Affected if The web administration interface is accessible and running
  3. Verify system log viewing feature is accessible
    Navigate to the system log viewing functionality within the web administration interface. Log in with valid administrator credentials and locate the log viewing section.
    Affected if The system log viewer is reachable via the web interface and accepts user input
  4. Check network exposure of web interface
    Review firewall rules or network access controls to determine if the web administration interface is exposed beyond trusted internal networks.
    Affected if The web interface is reachable from untrusted networks or the internet

A user is affected if their Avaya Communication Manager version is 3.1.x before 3.1.4 SP2 or 4.0.x before 4.0.3 SP1 and the web administration interface with log viewing 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 4.0.3 SP1 or later. Until patched, restrict web administration interface access to trusted admin accounts only via network segmentation or VPN.

Recommended fix High confidence

CM 3.1.4 SP2 (for 3.1.x line) or CM 4.0.3 SP1 (for 4.0.x line)

  1. 1. Identify the current Avaya Communication Manager version by accessing the system administration interface or checking system documentation
  2. 2. Schedule a maintenance window for the upgrade procedure
  3. 3. Backup all current system configurations and data according to Avaya backup procedures
  4. 4. For systems running CM 3.1.x (3.1, 3.1.1, 3.1.2, 3.1.3): Upgrade to CM 3.1.4 SP2 or later
  5. 5. Alternatively, for systems running CM 4.0.x: Upgrade to CM 4.0.3 SP1 or later
  6. 6. Verify the upgrade was successful by checking the version in the administration interface
  7. 7. Test that the web administration interface and log viewing functionality work correctly
  8. 8. Validate that the command execution vulnerability is no longer present
Caveat Upgrading major versions of Avaya Communication Manager may require configuration review and compatibility testing with integrated telephony systems

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

Fix this in Communication Manager 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 help mitigating

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-2008-6711 — 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-6711 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