dbcve.org
Communication ManagerApplication · Avaya

CVE-2008-6573

MEDIUM · 6.8 CVSS v2.0 Published 2009-04-01
Fix available
A fix is available. Upgrade to after 3.1 or later.
See remediation →
77/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
Multiple SQL injection vulnerabilities in Avaya SIP Enablement Services (SES) in Avaya Avaya Communication Manager 3.x, 4.0, and 5.0 (1) allow remote attackers to execute arbitrary SQL commands via unspecified vectors related to profiles in the SIP Personal Information Manager (SPIM) in the web interface; and allow remote authenticated users to execute arbitrary SQL commands via unspecified vectors related to (2) permissions for SPIM profiles in the web interface and (3) a crafted SIP request to the SIP server.

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

Multiple SQL injection vulnerabilities in Avaya SIP Enablement Services allow remote attackers to inject arbitrary SQL commands via the SIP Personal Information Manager (SPIM) web interface profiles, and authenticated users via SPIM profile permissions and crafted SIP requests to the server.

MitigationUpgrade to a patched version of Avaya Communication Manager or apply vendor-provided security patches; implement input validation/sanitization on SPIM profile parameters and SIP request handling as a compensating control.

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

AV:N/AC:M/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
    Locate the installed version of Avaya Communication Manager on the system. This is typically displayed in the system administration interface, or can be retrieved via CLI commands specific to Avaya CM (such as 'software' or 'version' commands in the maintenance shell). Compare the installed version to the affected ranges: <= 3.1, 3.1.1, 3.1.2, 3.1.3, 3.1.4, 3.1.5, 4.0, or 5.0.
    Affected if The installed version matches any of the listed affected versions (3.1.x through 5.0).
  2. Determine if SPIM web interface is enabled
    Check whether the SIP Personal Information Manager (SPIM) web interface component is installed and enabled on the Avaya system. This is typically configured in the web services or SIP enablement settings within the Avaya Administration interface.
    Affected if The SPIM web interface is enabled and accessible over the network.
  3. Verify SIP services are exposed
    Determine if the SIP Enablement Services are running and reachable. Check for open ports or services related to SIP (typically port 5060 or configured SIP ports) and whether the SPIM profiles are accessible via HTTP/HTTPS.
    Affected if SIP services are running and the SPIM web interface is network-accessible (even if behind authentication).
  4. Check for unauthenticated profile access
    Attempt to access SPIM profile functionality without credentials, or verify through access logs whether unauthenticated requests to profile endpoints have been observed. This can be done by reviewing web server access logs for SPIM-related paths.
    Affected if The SPIM profile interface allows unauthenticated access or shows signs of injection attempts in logs.

The environment is affected if Avaya Communication Manager version is 3.1.x through 5.0 AND the SPIM web interface is enabled and accessible, as the SQL injection flaws exist in the SPIM profile handling code.

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 a release after 3.1
Interim mitigation

Upgrade to a patched version of Avaya Communication Manager or apply vendor-provided security patches; implement input validation/sanitization on SPIM profile parameters and SIP request handling as a compensating control.

Fix this in Communication Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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