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

> Integer overflows in nedmalloc allow attackers to trigger buffer overflows via large size values, potentially leading to code execution or denial of service.

- **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 stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 25 Jul 2012
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-2whv-w9wx-38wp

## What is CVE-2012-2675?

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

### Official description

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

Weakness: CWE-189

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

It affects 1 product.


Products: Nedprod Nedmalloc.

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

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

## Is CVE-2012-2675 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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