# CVE-2012-4505: Memory corruption in n/a

> A heap-based buffer overflow in libproxy allows remote attackers to cause denial of service or execute arbitrary code via a crafted HTTP response.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Nov 2012
- **Updated:** 6 Aug 2024
- **Also known as:** CVE-2012-4521, DEBIAN-CVE-2012-4505, DSA-2571-1, GHSA-8g7q-m58p-3p6w, RHSA-2012:1461

## What is CVE-2012-4505?

CVE-2012-4505 is a critical memory corruption vulnerability in n/a, published on 11 Nov 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Heap-based buffer overflow in the px_pac_reload function in lib/pac.c in libproxy 0.2.x and 0.3.x allows remote servers to have an unspecified impact via a crafted Content-Length size in an HTTP response header for a proxy.pac file request, a different vulnerability than CVE-2012-4504.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libproxy` | Red Hat:enterprise_linux:6::client | All versions | 0:0.3.0-3.el6_3 |
| `libproxy-bin` | Red Hat:enterprise_linux:6::client | All versions | 0:0.3.0-3.el6_3 |
| `libproxy-debuginfo` | Red Hat:enterprise_linux:6::client | All versions | 0:0.3.0-3.el6_3 |
| `libproxy-devel` | Red Hat:enterprise_linux:6::client | All versions | 0:0.3.0-3.el6_3 |
| `libproxy-gnome` | Red Hat:enterprise_linux:6::client | All versions | 0:0.3.0-3.el6_3 |
| `libproxy-kde` | Red Hat:enterprise_linux:6::client | All versions | 0:0.3.0-3.el6_3 |
| `libproxy-mozjs` | Red Hat:enterprise_linux:6::client | All versions | 0:0.3.0-3.el6_3 |
| `libproxy-python` | Red Hat:enterprise_linux:6::client | All versions | 0:0.3.0-3.el6_3 |
| `libproxy-webkit` | Red Hat:enterprise_linux:6::client | All versions | 0:0.3.0-3.el6_3 |
| `libproxy` | Red Hat:enterprise_linux:6::computenode | All versions | 0:0.3.0-3.el6_3 |
| `libproxy-bin` | Red Hat:enterprise_linux:6::computenode | All versions | 0:0.3.0-3.el6_3 |
| `libproxy-debuginfo` | Red Hat:enterprise_linux:6::computenode | All versions | 0:0.3.0-3.el6_3 |
| `libproxy-devel` | Red Hat:enterprise_linux:6::computenode | All versions | 0:0.3.0-3.el6_3 |
| `libproxy-gnome` | Red Hat:enterprise_linux:6::computenode | All versions | 0:0.3.0-3.el6_3 |
| `libproxy-kde` | Red Hat:enterprise_linux:6::computenode | All versions | 0:0.3.0-3.el6_3 |
| `libproxy-mozjs` | Red Hat:enterprise_linux:6::computenode | All versions | 0:0.3.0-3.el6_3 |
| `libproxy-python` | Red Hat:enterprise_linux:6::computenode | All versions | 0:0.3.0-3.el6_3 |
| `libproxy-webkit` | Red Hat:enterprise_linux:6::computenode | All versions | 0:0.3.0-3.el6_3 |
| `libproxy` | Red Hat:enterprise_linux:6::server | All versions | 0:0.3.0-3.el6_3 |
| `libproxy-bin` | Red Hat:enterprise_linux:6::server | All versions | 0:0.3.0-3.el6_3 |
| `libproxy-debuginfo` | Red Hat:enterprise_linux:6::server | All versions | 0:0.3.0-3.el6_3 |
| `libproxy-devel` | Red Hat:enterprise_linux:6::server | All versions | 0:0.3.0-3.el6_3 |
| `libproxy-gnome` | Red Hat:enterprise_linux:6::server | All versions | 0:0.3.0-3.el6_3 |
| `libproxy-kde` | Red Hat:enterprise_linux:6::server | All versions | 0:0.3.0-3.el6_3 |
| `libproxy-mozjs` | Red Hat:enterprise_linux:6::server | All versions | 0:0.3.0-3.el6_3 |
| `libproxy-python` | Red Hat:enterprise_linux:6::server | All versions | 0:0.3.0-3.el6_3 |
| `libproxy-webkit` | Red Hat:enterprise_linux:6::server | All versions | 0:0.3.0-3.el6_3 |
| `libproxy` | Red Hat:enterprise_linux:6::workstation | All versions | 0:0.3.0-3.el6_3 |
| `libproxy-bin` | Red Hat:enterprise_linux:6::workstation | All versions | 0:0.3.0-3.el6_3 |
| `libproxy-debuginfo` | Red Hat:enterprise_linux:6::workstation | All versions | 0:0.3.0-3.el6_3 |
| `libproxy-devel` | Red Hat:enterprise_linux:6::workstation | All versions | 0:0.3.0-3.el6_3 |
| `libproxy-gnome` | Red Hat:enterprise_linux:6::workstation | All versions | 0:0.3.0-3.el6_3 |
| `libproxy-kde` | Red Hat:enterprise_linux:6::workstation | All versions | 0:0.3.0-3.el6_3 |
| `libproxy-mozjs` | Red Hat:enterprise_linux:6::workstation | All versions | 0:0.3.0-3.el6_3 |
| `libproxy-python` | Red Hat:enterprise_linux:6::workstation | All versions | 0:0.3.0-3.el6_3 |
| `libproxy-webkit` | Red Hat:enterprise_linux:6::workstation | All versions | 0:0.3.0-3.el6_3 |

Products: Libproxy Project Libproxy.

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

Upgrade to a fixed version.

## Is CVE-2012-4505 being exploited?

There is no known exploitation of CVE-2012-4505 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-5580](https://insights.sbomify.com/CVE-2012-5580/): Code injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-4505 is a critical memory corruption vulnerability in n/a, published on 11 Nov 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-4505 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-4505/ (Markdown: https://insights.sbomify.com/CVE-2012-4505/index.md)
```

## Sources

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

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