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

> A format string vulnerability in libproxy allows attackers to cause crashes or execute arbitrary code via malicious proxy names in environment variables or PAC files.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Oct 2014
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2012-5580, GHSA-mccr-h554-3wjw

## What is CVE-2012-5580?

CVE-2012-5580 is a high-severity code injection vulnerability in n/a, published on 27 Oct 2014. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Format string vulnerability in the print_proxies function in bin/proxy.c in libproxy 0.3.1 might allow context-dependent attackers to cause a denial of service (crash) and possibly execute arbitrary code via format string specifiers in a proxy name, as demonstrated using the http_proxy environment variable or a PAC file.

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

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

It affects 1 product.


Products: Libproxy Project Libproxy.

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

Upgrade to a fixed version.

## Is CVE-2012-5580 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-4504](https://insights.sbomify.com/CVE-2012-4504/): Memory corruption in n/a (critical 10.0)
- [CVE-2012-4505](https://insights.sbomify.com/CVE-2012-4505/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-5580 is a high-severity code injection vulnerability in n/a, published on 27 Oct 2014. 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-5580 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-5580/ (Markdown: https://insights.sbomify.com/CVE-2012-5580/index.md)
```

## Sources

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

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