dbcve.org
Spa 501g FirmwareOperating system · Cisco

CVE-2017-12260

HIGH · 7.5 CVSS v3.0 Published 2017-10-19
Fix available
A fix is available. Upgrade to after 7.6.2 or later.
See remediation →
84/100
Remediation priority · High
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
A vulnerability in the implementation of Session Initiation Protocol (SIP) functionality in Cisco Small Business SPA50x, SPA51x, and SPA52x Series IP Phones could allow an unauthenticated, remote attacker to cause an affected device to become unresponsive, resulting in a denial of service (DoS) condition. The vulnerability is due to the improper handling of SIP request messages by an affected device. An attacker could exploit this vulnerability by using formatted specifiers in a SIP payload that is sent to an affected device. A successful exploit could allow the attacker to cause the affected device to become unresponsive, resulting in a DoS condition that persists until the device is restarted manually. This vulnerability affects Cisco Small Business SPA50x, SPA51x, and SPA52x Series IP Phones that are running firmware release 7.6.2SR1 or earlier. Cisco Bug IDs: CSCvc63986.

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

A vulnerability in the SIP implementation of Cisco Small Business SPA50x, SPA51x, and SPA52x Series IP Phones allows an unauthenticated remote attacker to cause device DoS by sending SIP requests containing format specifiers in the payload. The affected device becomes unresponsive and requires manual restart.

MitigationUpgrade Cisco IP phone firmware beyond release 7.6.2SR1. Additionally, restrict SIP port (5060/UDP) access from untrusted networks using firewall rules or VoIP-specific filtering to block malicious SIP messages.

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 501g FirmwareOperating system
Affected:<= 7.6.2
Spa 502g FirmwareOperating system
Affected:<= 7.6.2
Spa 504g FirmwareOperating system
Affected:<= 7.6.2
Spa 508g FirmwareOperating system
Affected:<= 7.6.2
Spa 509g FirmwareOperating system
Affected:<= 7.6.2
Spa 512g FirmwareOperating system
Affected:<= 7.6.2
Spa 514g FirmwareOperating system
Affected:<= 7.6.2
Spa 525g FirmwareOperating system
Affected:<= 7.6.2

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the IP phone model
    Access the phone's web interface or check the device label. Look for model numbers SPA50x, SPA51x, or SPA52x series such as SPA501g, SPA502g, SPA504g, SPA508g, SPA509g, SPA512g, SPA514g, or SPA525g.
    Affected if The device model is one of the listed affected models (SPA501g, SPA502g, SPA504g, SPA508g, SPA509g, SPA512g, SPA514g, or SPA525g).
  2. Check the firmware version
    Log into the phone's web admin interface and navigate to the Status or Administration page. Locate the firmware version field. Alternatively, you may retrieve it via SIP OPTIONS request or from the device's backup/config file.
    Affected if The firmware version is 7.6.2 or earlier.
  3. Verify SIP service is enabled
    Check the phone's configuration page under SIP settings or Line settings. Confirm that SIP protocol is enabled for at least one line. You can also verify by scanning for UDP port 5060 listening on the device.
    Affected if SIP is enabled and the device is registered to a SIP server or awaiting calls.
  4. Assess network exposure of SIP port
    Check firewall rules or network configuration to determine if UDP port 5060 (SIP) is accessible from outside the trusted network. Review ACLs, port forwards, or VoIP gateway configurations.
    Affected if UDP port 5060 is exposed to untrusted or external networks without filtering.

A user is affected if they own one of the listed Cisco SPA models running firmware version 7.6.2 or lower, with SIP enabled and the SIP port potentially reachable from untrusted networks.

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
Upgrade available Upgrade to a release after 7.6.2
Interim mitigation

Upgrade Cisco IP phone firmware beyond release 7.6.2SR1. Additionally, restrict SIP port (5060/UDP) access from untrusted networks using firewall rules or VoIP-specific filtering to block malicious SIP messages.

Fix this in Spa 501g Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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