# CVE-2012-4459: Integer overflow in n/a

> Remote attackers can cause a denial of service in Apache Qpid via a crafted message triggering an integer overflow and out-of-bounds read.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Mar 2013
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-f4gr-qh9c-r8fg, UBUNTU-CVE-2012-4459

## What is CVE-2012-4459?

CVE-2012-4459 is a medium-severity vulnerability in n/a, published on 12 Mar 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Integer overflow in the qpid::framing::Buffer::checkAvailable function in Apache Qpid 0.20 and earlier allows remote attackers to cause a denial of service (crash) via a crafted message, which triggers an out-of-bounds read.

Weakness: CWE-189

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

It affects 1 product.


Products: Apache Qpid.

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

Upgrade to a fixed version.

## Is CVE-2012-4459 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-0224](https://insights.sbomify.com/CVE-2015-0224/): Denial of service in n/a (high 7.5)
- [CVE-2011-3620](https://insights.sbomify.com/CVE-2011-3620/): Auth bypass in n/a (high 7.5)
- [CVE-2019-0223](https://insights.sbomify.com/CVE-2019-0223/): Security feature bypass in Apache Qpid Proton (high 7.4)
- [CVE-2012-4446](https://insights.sbomify.com/CVE-2012-4446/): Improper Authentication in Apache Qpid (medium 6.8)
- [CVE-2015-0203](https://insights.sbomify.com/CVE-2015-0203/): Denial of service in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-4459 is a medium-severity vulnerability in n/a, published on 12 Mar 2013. 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-4459 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-4459/ (Markdown: https://insights.sbomify.com/CVE-2012-4459/index.md)
```

## Sources

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

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