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

> Remote attackers can cause denial of service or execute arbitrary code via crafted PDUs triggering integer overflows and buffer overflows in libpcp.

- **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:** 27 Aug 2012
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2012-3418, GHSA-wh7h-j72f-r8p8

## What is CVE-2012-3418?

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

### Official description

libpcp in Performance Co-Pilot (PCP) before 3.6.5 allows remote attackers to cause a denial of service and possibly execute arbitrary code via (1) a PDU with the numcreds field value greater than the number of actual elements to the __pmDecodeCreds function in p_creds.c; (2) the string byte number value to the __pmDecodeNameList function in p_pmns.c; (3) the numids value to the __pmDecodeIDList function in p_pmns.c; (4) unspecified vectors to the __pmDecodeProfile function in p_profile.c; the (5) status number value or (6) string number value to the __pmDecodeNameList function in p_pmns.c; (7) certain input to the __pmDecodeResult function in p_result.c; (8) the name length field (namelen) to the DecodeNameReq function in p_pmns.c; (9) a crafted PDU_FETCH request to the __pmDecodeFetch function in p_fetch.c; (10) the namelen field in the __pmDecodeInstanceReq function in p_instance.c; (11) the buflen field to the __pmDecodeText function in p_text.c; (12) PDU_INSTANCE packets to the __pmDecodeInstance in p_instance.c; or the (13) c_numpmid or (14) v_numval fields to the __pmDecodeLogControl function in p_lcontrol.c, which triggers integer overflows, heap-based buffer overflows, and/or buffer over-reads.

Weakness: CWE-189

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

It affects 1 product.


Products: Sgi Performance Co-Pilot.

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

Upgrade to a fixed version.

## Is CVE-2012-3418 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2001-0823](https://insights.sbomify.com/CVE-2001-0823/): Path traversal in n/a (high 7.2)
- [CVE-2012-3419](https://insights.sbomify.com/CVE-2012-3419/): Information disclosure in n/a (medium 5.0)
- [CVE-2012-3420](https://insights.sbomify.com/CVE-2012-3420/): Denial of service in n/a (medium 5.0)
- [CVE-2012-3421](https://insights.sbomify.com/CVE-2012-3421/): Denial of service in n/a (medium 5.0)
- [CVE-2012-5530](https://insights.sbomify.com/CVE-2012-5530/): Path traversal in n/a (low 2.1)

## Fix prompt for AI coding agents

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

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

## Sources

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

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