Unified Ip Phones 9900 Series FirmwareOperating system · Cisco
CVE-2013-3426
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 · uneditedThe Serviceability servlet on Cisco 9900 IP phones does not properly restrict paths, which allows remote attackers to read arbitrary files by specifying a pathname in a file request, aka Bug ID CSCuh52810.
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 confidenceThe Serviceability servlet on Cisco 9900 IP phones contains a path traversal vulnerability that fails to properly restrict file paths, allowing remote attackers to read arbitrary files on the device by manipulating pathname parameters in HTTP requests to the servlet.
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
Unified Ip Phones 9900 Series FirmwareOperating system
all versions
Unified Ip Phone 9951Hardware / appliance
all versions
Unified Ip Phone 9971Hardware / appliance
all versionsCVSS 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
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the phone modelAccess the phone's web interface by navigating to the phone's IP address, or check the phone display for the model number. Common paths include / or /homepage.htm which often display device information including model number.Affected if The phone model is Cisco Unified IP Phone 9900 Series, 9951, or 9971
-
Verify the Serviceability servlet is accessibleSend an HTTP GET request to the phone's IP address on common management ports (80, 443, 8080). Try accessing paths like /Serviceability or /index.htm to confirm the management interface is reachable.Affected if The phone's web management interface responds to HTTP requests
-
Test for path traversal vulnerabilitySend an HTTP GET request to the Serviceability servlet with a path traversal payload such as /Services/Serviceability?file=../../../../../../etc/passwd or similar path patterns. A vulnerable device will return file contents instead of an error.Affected if The servlet returns the contents of system files or allows reading files outside the expected directory
-
Check network exposure of management interfaceReview firewall rules or network segmentation to determine if the phone's management HTTP port (typically 80/443) is exposed to untrusted networks or the internet.Affected if The phone's management interface is accessible from untrusted networks
A user is affected if they operate a Cisco Unified IP Phone 9900 Series, 9951, or 9971 with the Serviceability servlet enabled and network-accessible, as all firmware versions of these models contain the path traversal vulnerability.
Generated from the published advisory. Verify against your own configuration.
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 dataApply the vendor patch from Cisco, or if the Serviceability servlet is not required, disable it. Restrict network access to the management interfaces of affected phones to prevent unauthorized access.
Fix this in Unified Ip Phones 9900 Series Firmware
Scoped from the published advisory
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-3426 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2013-3426 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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