dbcve.org
Sip Enablement ServicesApplication · Avaya

CVE-2008-6707

MEDIUM · 6.4 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 →
73/100
Remediation priority · Elevated
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
The Web management interface in Avaya SIP Enablement Services (SES) 3.x and 4.0, as used with Avaya Communication Manager 3.1.x, does not perform authentication for certain functionality, which allows remote attackers to obtain sensitive information and access restricted functionality via (1) the certificate installation utility, (2) unspecified scripts in the objects folder, (3) an "unnecessary default application," (4) unspecified scripts in the states folder, (5) an unspecified "default application" that lists server configuration, and (6) "full system help."

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 · high confidence

The Avaya SIP Enablement Services (SES) 3.x and 4.0 web management interface fails to enforce authentication on multiple endpoints including certificate installation utilities, scripts in objects/states folders, and certain default applications. This allows unauthenticated remote attackers to access sensitive system configuration information and restricted management functionality.

MitigationRestrict network access to the SES management interface to trusted internal IPs only, disable unnecessary default applications and exposed scripts, and apply vendor-provided patches for this authentication bypass vulnerability.

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
Sip Enablement ServicesApplication
Affected:= 3.0= 3.1= 3.1.1= 4.0
Communication ManagerApplication
Affected:= 3.1= 3.1.1= 3.1.2= 3.1.3= 3.1.4= 3.1.5

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
None

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

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 SES version
    Check the version of Avaya SIP Enablement Services installed on the system by reviewing system inventory, installed software list, or the about page of the SES web management interface
    Affected if The installed version is 3.0, 3.1, 3.1.1, or 4.0
  2. Identify installed Avaya Communication Manager version
    Check the version of Avaya Communication Manager installed by reviewing system inventory or checking the CM administration interface
    Affected if The installed version is 3.1, 3.1.1, 3.1.2, 3.1.3, 3.1.4, or 3.1.5
  3. Confirm web management interface is accessible
    Attempt to reach the SES web management interface over HTTP/HTTPS from a network location
    Affected if The web interface is reachable and responds to requests
  4. Test certificate installation utility access
    Attempt to access the certificate installation utility endpoint (such as /certinst or similar certificate-related paths) without providing any authentication credentials
    Affected if The endpoint returns sensitive configuration data or allows management actions without being prompted for login
  5. Test objects/states scripts access
    Attempt to access scripts in the objects/states folders (such as /objects/ or /states/ paths) without authentication
    Affected if These scripts are accessible and return system information or allow configuration changes without authentication
  6. Test default applications access
    Attempt to access default applications that ship with the SES installation without authentication
    Affected if These applications are accessible and expose management functionality without requiring credentials

A system is affected if it runs any of the listed Avaya SES (3.0-4.0) or Communication Manager (3.1-3.1.5) versions AND the web management interface is exposed with unauthenticated access to certificate utilities, objects/states scripts, or default applications.

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

Restrict network access to the SES management interface to trusted internal IPs only, disable unnecessary default applications and exposed scripts, and apply vendor-provided patches for this authentication bypass vulnerability.

Fix this in Sip Enablement Services Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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