dbcve.org
Spa500 FirmwareOperating system · Cisco

CVE-2015-0670

MEDIUM · 6.4 CVSS v2.0 Published 2015-03-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/100
Remediation priority · Elevated
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
The default configuration of Cisco Small Business IP phones SPA 300 7.5.5 and SPA 500 7.5.5 does not properly support authentication, which allows remote attackers to read audio-stream data or originate telephone calls via a crafted XML request, aka Bug ID CSCuo52482.

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

This vulnerability in Cisco Small Business IP phones SPA 300 and SPA 500 (version 7.5.5) stems from the default configuration not properly implementing authentication. Attackers can send crafted XML requests to the phone's web interface without credentials, enabling them to either intercept audio stream data (confidentiality impact) or originate outbound telephone calls (integrity impact). The attack is network-based and requires no authentication.

MitigationEnable proper authentication on the phone web interface and disable unauthenticated XML request handling. Alternatively, network-segment phone management interfaces to restrict access to trusted management stations only. Apply any available vendor firmware updates.

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
Spa500 FirmwareOperating system
Affected:= 7.5.5
Spa 501g 8 Line Ip PhoneHardware / appliance
Affected:all versions
Spa 502g 1 Line Ip PhoneHardware / appliance
Affected:all versions
Spa 504g 4 Line Ip PhoneHardware / appliance
Affected:all versions
Spa 508g 8 Line Ip PhoneHardware / appliance
Affected:all versions
Spa 509g 12 Line Ip PhoneHardware / appliance
Affected:all versions
Spa 512g 1 Line Ip PhoneHardware / appliance
Affected:all versions
Spa 514g 4 Line Ip PhoneHardware / appliance
Affected:all versions

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
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
None

AV:N/AC:L/Au:N/C:P/I:P/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 checks

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

  1. Identify the phone model and firmware version
    Access the phone's web administration interface (typically http://<phone-ip>/) and navigate to the Admin or System Status page to view the model number and running firmware version. Alternatively, use the phone's LCD screen menu under Admin Settings > Product Info.
    Affected if The model is any Cisco SPA 300 or SPA 500 series (SPA500, SPA501g, SPA502g, SPA504g, SPA508g, SPA509g, SPA512g, SPA514g) and the firmware is version 7.5.5 or any version for the models listed as 'all versions'.
  2. Verify web interface network accessibility
    Confirm whether the phone's web management interface is reachable from network segments other than trusted management VLANs. Attempt to access http://<phone-ip>/ from a non-trusted network location or scan the phone's IP for open HTTP/HTTPS ports.
    Affected if The web interface is exposed to untrusted network segments, making it reachable by potential attackers.
  3. Check if XML request handling is enabled
    Log into the phone's web admin interface and locate the XML or Remote Management settings (typically under Administration > XML Service or similar). Verify whether the service allows unauthenticated XML requests.
    Affected if XML service or remote XML request handling is enabled without requiring authentication credentials.
  4. Confirm authentication is enforced on web interface
    Navigate to the phone's security or administrator settings and verify that web access authentication is enabled. Attempt to access privileged functions or XML endpoints without providing credentials.
    Affected if The web interface allows access to administrative functions or XML endpoints without requiring valid authentication credentials (default/unconfigured state).

Your environment is affected if you are running any Cisco SPA 300 or SPA 500 series phone on firmware 7.5.5 or all versions for the specific models listed, with the web interface network-accessible and XML request handling enabled without authentication enforcement.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Enable proper authentication on the phone web interface and disable unauthenticated XML request handling. Alternatively, network-segment phone management interfaces to restrict access to trusted management stations only. Apply any available vendor firmware updates.

Fix this in Spa500 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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