Unified Ip Phones 9900 Series FirmwareOperating system · Cisco
CVE-2014-0658
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 · uneditedCisco 9900 Unified IP phones allow remote attackers to cause a denial of service (unregistration) via a crafted SIP header, aka Bug ID CSCul24898.
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 confidenceThe vulnerability allows remote attackers to cause a denial of service on Cisco 9900 Unified IP phones by sending specially crafted SIP (Session Initiation Protocol) headers. This causes affected phones to become unregistered from the VoIP infrastructure, disrupting communication services.
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
- High
- Authentication
- None
- Confidentiality
- None
- Integrity
- None
- Availability
- Complete
AV:N/AC:H/Au:N/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify your phone modelPhysically inspect the phone or access its web/admin interface to determine the exact model numberAffected if Model is Cisco Unified IP Phone 9951, 9971, or any 9900 Series phone (9901, 9902, 9905, 9915, 9925, etc.)
-
Confirm SIP protocol is enabledCheck the phone's configuration or registration status to verify if it is using SIP (Session Initiation Protocol) for VoIP calls. This is typically visible in the phone's admin settings or network registration statusAffected if SIP is enabled and the phone is registered to a SIP-based VoIP infrastructure (as opposed to SCCP/Skinny protocol)
-
Verify phone network exposureDetermine if the phone's SIP interface is reachable from network segments that contain untrusted users or the internet. Check network firewall rules and VLAN placementAffected if The phone can receive SIP traffic from untrusted network sources or the SIP port (typically UDP/TCP 5060) is exposed outside the trusted network
You are affected if you have a Cisco Unified IP Phone 9951, 9971, or any 9900 Series phone that is using SIP for VoIP registration and can receive SIP traffic from potential attackers.
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 dataImplement SIP traffic filtering and rate limiting at network boundaries to block malformed SIP messages. Check for available firmware updates from Cisco for the 9900 Unified IP phone series and apply appropriate patches.
Fix this in Unified Ip Phones 9900 Series Firmware
Scoped from the published advisory
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-0658 — 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-2014-0658 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