Small Business Ip Phone FirmwareApplication · Cisco
CVE-2012-0333
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 Small Business IP phones with SPA 500 series firmware 7.4.9 and earlier do not require authentication for Push XML requests, which allows remote attackers to make telephone calls via an XML document, aka Bug ID CSCts08768.
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 confidenceCisco Small Business IP phones in the SPA 500 series running firmware 7.4.9 and earlier do not require authentication for Push XML requests. This allows remote attackers to make unsolicited telephone calls by sending specially crafted XML documents to the phone without any credentials.
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
Small Business Ip Phone FirmwareApplication
<= 7.4.9= 7.1.7= 7.2.5= 7.3.5= 7.4.3= 7.4.4= 7.4.5= 7.4.6= 7.4.7= 7.4.8
Small Business Ip PhoneHardware / appliance
= spa525g= spa525g2CVSS 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
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the phone modelAccess the phone's web administration interface and locate the device information or status page to confirm the model is a Cisco SPA 500 series device, specifically spa525g or spa525g2Affected if The device model is spa525g or spa525g2 in the SPA 500 series
-
Check the firmware versionIn the phone's web admin interface, navigate to the firmware or software version information section and note the installed firmware version numberAffected if The firmware version is 7.4.9 or earlier, or exactly 7.1.7, 7.2.5, 7.3.5, 7.4.3, 7.4.4, 7.4.5, 7.4.6, 7.4.7, or 7.4.8
-
Verify Push XML functionality statusLocate the Push XML or XML service settings in the phone's administrative web interface, typically found under application, XML, or service configuration menus, and determine whether the Push XML feature is enabledAffected if Push XML service is enabled on the device
-
Assess network accessibilityDetermine if the phone's management web interface is reachable from untrusted network segments by checking firewall rules, VLAN configuration, or attempting to access the phone's IP address from an external networkAffected if The phone's administrative interface is accessible from untrusted networks without network segmentation or filtering
The device is affected if it is a Cisco SPA 500 series phone (spa525g/spa525g2) running firmware 7.4.9 or earlier, has Push XML enabled, and is accessible from networks where untrusted actors could send XML requests.
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 dataUpdate the SPA 500 series firmware to a version newer than 7.4.9. If immediate updates are not feasible, restrict network access to the phone management interfaces using firewalls or VLANs to prevent unauthorized Push XML requests.
Fix this in Small Business Ip Phone Firmware
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-0333 — 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-2012-0333 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