# CVE-2012-0333: Auth bypass in n/a

> Remote attackers can make unauthorized telephone calls on Cisco Small Business IP phones due to missing authentication for Push XML requests.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 May 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-c544-2mq8-fpf3

## What is CVE-2012-0333?

CVE-2012-0333 is a medium-severity authentication bypass vulnerability in n/a, published on 2 May 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Cisco 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.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2012-0333?

It affects 2 products.


Products: Cisco Small Business Ip Phone, Cisco Small Business Ip Phone Firmware.

## How do I fix CVE-2012-0333?

No fix has been published for CVE-2012-0333 yet. Limit exposure of the affected software until one is available.

## Is CVE-2012-0333 being exploited?

There is no known exploitation of CVE-2012-0333 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-0333 and fix it if it is affected.

What it is: CVE-2012-0333 is a medium-severity authentication bypass vulnerability in n/a, published on 2 May 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2012-0333 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2012-0333/ (Markdown: https://insights.sbomify.com/CVE-2012-0333/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2012-0333
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2012-0333
- OSV: https://osv.dev/vulnerability/CVE-2012-0333

---
From sbomify Insights: https://insights.sbomify.com/CVE-2012-0333/
Summaries are generated and may contain mistakes; the official description above is the record.