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

> Integer overflows in Hoard allocator allow attackers to trigger buffer overflows and potential code execution by supplying large size values.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Jul 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-hxjr-hj59-c5fm

## What is CVE-2012-2676?

CVE-2012-2676 is a medium-severity vulnerability in n/a, published on 25 Jul 2012. 

### Official description

Multiple integer overflows in the (1) malloc and (2) calloc functions in Hoard before 3.9 make it easier for context-dependent attackers to perform memory-related attacks such as buffer overflows on implementing code via a large size value, which causes less memory to be allocated than expected.

Weakness: CWE-189

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

It affects 1 product.


Products: Emery Berger Hoard.

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

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

## Is CVE-2012-2676 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2012-2676 is a medium-severity vulnerability in n/a, published on 25 Jul 2012. 
Exploitation: There is no known exploitation of CVE-2012-2676 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-2676/ (Markdown: https://insights.sbomify.com/CVE-2012-2676/index.md)
```

## Sources

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

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