dbcve.org
Communication ManagerApplication · Avaya

CVE-2008-6574

HIGH · 7.5 CVSS v2.0 Published 2009-04-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 SIP Enablement Services (SES) in Avaya Communication Manager 3.1.x and 4.x allows remote attackers to gain privileges and cause a denial of service via unknown vectors related to reuse of valid 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

Vulnerability in Avaya Communication Manager's SIP Enablement Services (SES) allows remote attackers to gain elevated privileges and cause denial of service through unknown vectors related to improper reuse of valid credentials. The credential reuse issue suggests sessions or authentication tokens may not be properly validated or regenerated, allowing attackers to hijack legitimate sessions.

MitigationApply vendor patches for Avaya Communication Manager 4.x or upgrade to a supported version; if patches are unavailable, restrict network access to SES ports using firewalls or network segmentation to limit exposure to untrusted networks.

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= 3.1.5= 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
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

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

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
    Check the installed version of Avaya Communication Manager on the system. On the management interface or using system inventory commands, look for the exact version number.
    Affected if The installed version matches 3.1, 3.1.1, 3.1.2, 3.1.3, 3.1.4, 3.1.5, 4.0, 4.0.1, or 4.0.3.
  2. Confirm SIP Enablement Services (SES) is active
    Determine whether the SIP Enablement Services module is enabled and running on the Avaya system. This may be visible in the system services list, management console, or through SES-specific status commands.
    Affected if SES is installed and running on the affected Communication Manager version.
  3. Review SES authentication and session logs
    Examine the SIP Enablement Services logs for signs of session fixation, credential reuse, or unexpected session token patterns that could indicate hijacking attempts.
    Affected if Logs show reused credentials, unexpected session tokens, or authentication anomalies.
  4. Audit SES user accounts and sessions
    Review active SES user sessions and authentication records to identify any unauthorized or duplicate sessions that may indicate credential reuse exploitation.
    Affected if Multiple simultaneous sessions or sessions originating from unexpected sources are associated with legitimate credentials.
  5. Check network exposure of SES ports
    Identify which network ports SES listens on and determine if they are exposed to untrusted networks. SIP typically uses port 5060 and may use additional ports for related services.
    Affected if SES ports are accessible from untrusted networks without firewall protection.

You are affected if Avaya Communication Manager runs a version between 3.1 and 4.0.3 inclusive AND the SIP Enablement Services module is enabled, with exposed network 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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patches for Avaya Communication Manager 4.x or upgrade to a supported version; if patches are unavailable, restrict network access to SES ports using firewalls or network segmentation to limit exposure to untrusted networks.

Fix this in Communication Manager Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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