# CVE-2012-1328: Code injection in n/a

> Local attackers can inject data into Cisco Unified IP Phones to gain elevated privileges and execute arbitrary code.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 May 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-r6g3-3vwj-5r6x

## What is CVE-2012-1328?

CVE-2012-1328 is a medium-severity code injection vulnerability in n/a, published on 3 May 2012. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Cisco Unified IP Phones 9900 series devices with firmware 9.1 and 9.2 do not properly handle downloads of configuration information to an RT phone, which allows local users to gain privileges via unspecified injected data, aka Bug ID CSCts32237.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 2 products.


Products: Cisco Unified Ip Phone, Cisco Unified Ip Phone Firmware.

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

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

## Is CVE-2012-1328 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-6190](https://insights.sbomify.com/CVE-2007-6190/): Information disclosure in n/a (low 3.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-1328 is a medium-severity code injection vulnerability in n/a, published on 3 May 2012. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2012-1328 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-1328/ (Markdown: https://insights.sbomify.com/CVE-2012-1328/index.md)
```

## Sources

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

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