Spa 301 FirmwareOperating system · Cisco
CVE-2017-12219
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 · uneditedA vulnerability in the handling of IP fragments for the Cisco Small Business SPA300, SPA500, and SPA51x Series IP Phones could allow an unauthenticated, remote attacker to cause the device to reload unexpectedly, resulting in a denial of service (DoS) condition. The vulnerability is due to the inability to handle many large IP fragments for reassembly in a short duration. An attacker could exploit this vulnerability by sending a crafted stream of IP fragments to the targeted device. An exploit could allow the attacker to cause a DoS condition when the device unexpectedly reloads. Cisco Bug IDs: CSCve82586.
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 confidenceA vulnerability in IP fragment reassembly handling in Cisco SPA300, SPA500, and SPA51x Series IP Phones allows an unauthenticated remote attacker to send a crafted stream of large IP fragments that overwhelm the device's fragment buffer, causing an unexpected reload and denial of service.
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
Spa 301 FirmwareOperating system
= 7.6.2
Spa 303 FirmwareOperating system
= 7.6.2
Spa 500ds FirmwareOperating system
= 7.6.2
Spa 500s FirmwareOperating system
= 7.6.2
Spa 501g FirmwareOperating system
= 7.6.2
Spa 502g FirmwareOperating system
= 7.6.2
Spa 504g FirmwareOperating system
= 7.6.2
Spa 508g FirmwareOperating system
= 7.6.2CVSS 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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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 IP phone modelAccess the phone's web interface or check the physical device label to determine if it is a Cisco SPA300, SPA500, or SPA51x series model (such as SPA301, SPA303, SPA500ds, SPA500s, SPA501g, SPA502g, SPA504g, or SPA508g).Affected if The device is one of these specific models.
-
Check the firmware versionLogin to the phone's web admin interface and navigate to the Firmware Version or Product Information page. Alternatively, on the phone display, access the Admin login > Product Info > Firmware screen.Affected if The installed firmware version is exactly 7.6.2.
-
Verify network accessibilityConfirm the IP phone has an active network connection and is reachable on the network by pinging its IP address or checking that it is registered with your VoIP server.Affected if The phone is network-accessible and can receive IP packets from an attacker.
-
Confirm IP fragment handling is activeVerify the phone is processing IP traffic. The IP fragment reassembly feature is enabled by default on any IP-connected device - no specific configuration check is needed since the vulnerability is in the default fragment processing.Affected if The phone is handling IP network traffic, which is the default operational state.
You are affected if you have a Cisco SPA300, SPA500, or SPA51x series IP phone running firmware version exactly 7.6.2 that is network-accessible.
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 network-level filtering of excessive IP fragments at the perimeter (firewall/IPS) or apply any available Cisco firmware update for the affected phone series; consider network segmentation to limit exposure of phone devices to untrusted networks.
Fix this in Spa 301 Firmware
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-12219 — 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-2017-12219 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