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

> Heap-based buffer overflow in Perl's repeat operator allows attackers to cause denial of service or execute arbitrary code.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 18 Dec 2012
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2012-5195, GHSA-6768-qw7m-q528

## What is CVE-2012-5195?

CVE-2012-5195 is a high-severity memory corruption vulnerability in n/a, published on 18 Dec 2012. 

### Official description

Heap-based buffer overflow in the Perl_repeatcpy function in util.c in Perl 5.12.x before 5.12.5, 5.14.x before 5.14.3, and 5.15.x before 15.15.5 allows context-dependent attackers to cause a denial of service (memory consumption and crash) or possibly execute arbitrary code via the 'x' string repeat operator.

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

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

It affects 1 product.


Products: Perl Perl.

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

Upgrade to a fixed version.

## Is CVE-2012-5195 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2026-4176](https://insights.sbomify.com/CVE-2026-4176/): Supply chain in perl (critical 9.8)
- [CVE-2022-48522](https://insights.sbomify.com/CVE-2022-48522/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-12814](https://insights.sbomify.com/CVE-2017-12814/): Memory corruption in n/a (critical 9.8)
- [CVE-2015-8608](https://insights.sbomify.com/CVE-2015-8608/): Memory corruption in n/a (critical 9.8)
- [CVE-2026-13221](https://insights.sbomify.com/CVE-2026-13221/): Integer overflow in perl:perl (critical 9.1)

## Fix prompt for AI coding agents

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

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

## Sources

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

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