Unified Ip Phone 8945Hardware / appliance · Cisco
CVE-2013-3468
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 Cisco Unified IP Phone 8945 with software 9.3(2) allows remote attackers to cause a denial of service (device hang) via a malformed PNG file, aka Bug ID CSCud04270.
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 Cisco Unified IP Phone 8945 with firmware 9.3(2) contains a denial-of-service vulnerability in its PNG image parsing functionality. Remote attackers can send a malformed PNG file to the device, causing it to hang or become unresponsive. The attack requires no authentication and is network-exploitable, indicating the phone processes incoming image data without proper bounds checking or validation.
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 Phone 8945Hardware / appliance
all versions
Unified Ip Phone FirmwareOperating system
= 9.3CVSS 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
- None
- Integrity
- None
- Availability
- Complete
AV:N/AC:L/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 the device modelAccess the phone's web interface or administrative console, or use CDP/LLDP network discovery to confirm the device is a Cisco Unified IP Phone 8945Affected if The device model is Cisco Unified IP Phone 8945
-
Check the firmware versionOn the phone, navigate to Settings > Device Information > Firmware Version, or access the web interface at the phone's IP address and check the status or administration pageAffected if The firmware version is 9.3.x (particularly 9.3(2))
-
Verify network accessibilityConfirm the phone has an IP address on the network and is reachable via ping or telnet/http from untrusted network segmentsAffected if The phone is directly accessible from network segments where untrusted users or devices exist
-
Check for custom wallpaper/PNG configurationsReview the phone's configuration for any custom PNG wallpapers or image uploads configured via Cisco Unified Communications Manager or the phone's web interfaceAffected if Custom PNG images are loaded onto the device (though the vulnerability can also be triggered by incoming malformed PNG data)
You are affected if you have a Cisco Unified IP Phone 8945 running firmware 9.3.x that is network-accessible, as the vulnerability requires no authentication and can be triggered by sending a malformed PNG to the device.
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-supplied firmware patch from Cisco for Bug ID CSCud04270. If patches are unavailable, restrict network exposure of the phones and implement network segmentation to limit attack surface.
Fix this in Unified Ip Phone 8945
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2013-3468 — 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-3468 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