# CVE-2013-1969: Use after free in n/a

> Use-after-free flaws in libxml2 allow attackers to cause crashes or execute arbitrary code via crafted XML input.

- **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 needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Apr 2013
- **Updated:** 6 Aug 2024
- **Also known as:** CVE-2013-1970, GHSA-jmvg-2fg9-jhpr

## What is CVE-2013-1969?

CVE-2013-1969 is a high-severity use after free vulnerability in Xmlsoft Libxml2, published on 25 Apr 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple use-after-free vulnerabilities in libxml2 2.9.0 and possibly other versions might allow context-dependent attackers to cause a denial of service (crash) and possibly execute arbitrary code via vectors related to the (1) htmlParseChunk and (2) xmldecl_done functions, as demonstrated by a buffer overflow in the xmlBufGetInputBase function.

Weakness: CWE-399

## Which versions are affected by CVE-2013-1969?

It affects 1 product.


Products: Xmlsoft Libxml2.

## How do I fix CVE-2013-1969?

Upgrade to a fixed version.

## Is CVE-2013-1969 being exploited?

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

## Other vulnerabilities in Xmlsoft Libxml2

- [CVE-2017-16931](https://insights.sbomify.com/CVE-2017-16931/): XML external entity in n/a (critical 9.8)
- [CVE-2017-8872](https://insights.sbomify.com/CVE-2017-8872/): Information disclosure in n/a (critical 9.1)
- [CVE-2022-49043](https://insights.sbomify.com/CVE-2022-49043/): Use after free in libxml2 (high 8.1)
- [CVE-2026-86140](https://insights.sbomify.com/CVE-2026-86140/): Memory corruption in libxml2 (high 8.0)
- [CVE-2024-34459](https://insights.sbomify.com/CVE-2024-34459/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-1969 and fix it if it is affected.

What it is: CVE-2013-1969 is a high-severity use after free vulnerability in Xmlsoft Libxml2, published on 25 Apr 2013. 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-2013-1969 in the wild and no public exploit code.

Affected product: Xmlsoft Libxml2. 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-2013-1969/ (Markdown: https://insights.sbomify.com/CVE-2013-1969/index.md)
```

## Sources

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

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