# CVE-2012-1152: Denial of service in n/a

> Remote attackers can crash the application via format string specifiers in YAML input processed by the Perl YAML::LibYAML module.

- **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:** 9 Sep 2012
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2012-1152, DSA-2432-1, GHSA-3h7q-h379-g658

## What is CVE-2012-1152?

CVE-2012-1152 is a medium-severity denial of service vulnerability in n/a, published on 9 Sep 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple format string vulnerabilities in the error reporting functionality in the YAML::LibYAML (aka YAML-LibYAML and perl-YAML-LibYAML) module 0.38 for Perl allow remote attackers to cause a denial of service (process crash) via format string specifiers in a (1) YAML stream to the Load function, (2) YAML node to the load_node function, (3) YAML mapping to the load_mapping function, or (4) YAML sequence to the load_sequence function.

Weakness: CWE-134 (Use of Externally-Controlled Format String)

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

It affects 1 product.


Products: Ingy Yaml\.

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

Upgrade to a fixed version.

## Is CVE-2012-1152 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2012-1152 is a medium-severity denial of service vulnerability in n/a, published on 9 Sep 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-1152 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-1152/ (Markdown: https://insights.sbomify.com/CVE-2012-1152/index.md)
```

## Sources

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

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