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

> Remote authenticated administrators can execute arbitrary code on Cisco Digital Media Manager via crafted URLs.

- **Severity:** Critical 9.0 (`AV:N/AC:L/Au:S/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Jan 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-84c9-cjwm-w46g

## What is CVE-2012-0329?

CVE-2012-0329 is a critical code injection vulnerability in n/a, published on 19 Jan 2012. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Cisco Digital Media Manager 5.2.2 and earlier, and 5.2.3, allows remote authenticated users to execute arbitrary code via vectors involving a URL and an administrative resource, aka Bug ID CSCts63878.

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

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

It affects 1 product.


Products: Cisco Digital Media Manager.

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

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

## Is CVE-2012-0329 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2010-0570](https://insights.sbomify.com/CVE-2010-0570/): Hardcoded credentials in n/a (critical 10.0)
- [CVE-2010-0571](https://insights.sbomify.com/CVE-2010-0571/): Privilege escalation in n/a (high 8.5)
- [CVE-2010-0572](https://insights.sbomify.com/CVE-2010-0572/): Information disclosure in n/a (high 7.1)
- [CVE-2013-3446](https://insights.sbomify.com/CVE-2013-3446/): Open redirect in n/a (medium 5.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-0329 is a critical code injection vulnerability in n/a, published on 19 Jan 2012. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2012-0329 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-0329/ (Markdown: https://insights.sbomify.com/CVE-2012-0329/index.md)
```

## Sources

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

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