dbcve.org
Communication ManagerApplication · Avaya

CVE-2008-5709

HIGH · 9.0 CVSS v2.0 Published 2008-12-24
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
Multiple unspecified vulnerabilities in the web management interface in Avaya Communication Manager (CM) 3.1 before 3.1.4 SP2, 4.0 before 4.0.3 SP1, and 5.0 before 5.0 SP3 allow remote authenticated users to execute arbitrary code via unknown attack vectors in the (1) Set Static Routes and (2) Backup History components.

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

Authenticated remote code execution vulnerability in Avaya Communication Manager web management interface. The flaw exists in the Set Static Routes and Backup History components, allowing remote authenticated users to execute arbitrary code via unspecified attack vectors.

MitigationApply vendor patches: upgrade to CM 3.1.4 SP2, 4.0.3 SP1, or 5.0 SP3 or later. Until patched, restrict network access to the management interface to trusted networks only and minimize the number of authenticated users with access.

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.1= 3.1.2= 3.1.3= 3.1.4= 4.0= 4.0.1= 4.0.3= 5.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
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 system via CLI or administration interface and run the command to display the CM version (typically via 'version' or 'show system' command in the maintenance shell)
    Affected if The displayed version matches 3.1.1, 3.1.2, 3.1.3, 3.1.4, 4.0, 4.0.1, 4.0.3, or 5.0 exactly
  2. Confirm web management interface is enabled
    Check the system configuration for the web-based management interface status, typically accessible via port 443 or 8443 on the CM server
    Affected if The web management interface is enabled and accessible on the network
  3. Verify access to vulnerable components
    Log into the web management interface and navigate to the 'Set Static Routes' and 'Backup History' sections under the administration or network configuration areas
    Affected if These components are present and accessible within the web interface without additional security restrictions
  4. Assess network exposure of management interface
    Review firewall rules, ACLs, or network segmentation to determine if the web management interface is reachable from untrusted networks
    Affected if The web management interface is exposed to networks beyond trusted administration segments

A system is affected if it runs an affected CM version (3.1.x, 4.0.x, or 5.0) with the web management interface enabled and the Set Static Routes or Backup History components accessible to authenticated users.

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

Apply vendor patches: upgrade to CM 3.1.4 SP2, 4.0.3 SP1, or 5.0 SP3 or later. Until patched, restrict network access to the management interface to trusted networks only and minimize the number of authenticated users with access.

Recommended fix High confidence

Avaya Communication Manager 3.1.4 SP2 or later (for 3.x line); note that versions 4.0 before 4.0.3 SP1 and 5.0 before 5.0 SP3 are also affected

  1. 1. Identify the current installed version of Avaya Communication Manager via the web management interface or CLI
  2. 2. Schedule a maintenance window for the upgrade procedure
  3. 3. Perform a complete backup of the current Communication Manager configuration
  4. 4. Download Avaya Communication Manager version 3.1.4 SP2 (or later recommended version) from Avaya support portal
  5. 5. Apply the upgrade package following Avaya's documented upgrade procedures for the web management interface
  6. 6. Verify the upgrade was successful by checking the version number in the system
  7. 7. Test the Set Static Routes and Backup History components in the web management interface to confirm proper functionality
  8. 8. Verify that the system is no longer vulnerable to the input validation issues
Caveat Review Avaya release notes for 3.1.4 SP2 for any configuration or compatibility changes before upgrading

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

Fix this in Communication Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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