# CVE-2022-29824: Integer overflow in n/a

> Integer overflows in libxml2 buffer functions allow out-of-bounds writes when processing crafted multi-gigabyte XML files, potentially leading to code execution or crashes.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 3 May 2022
- **Updated:** 14 Oct 2026
- **Also known as:** ALPINE-CVE-2022-29824, AZL-9616, AZL-9617, CLSA-2022-1657816433, CLSA-2022-1657816650, CLSA-2022-1660064066, DEBIAN-CVE-2022-29824, DLA-3012-1, DSA-5142-1, ECHO-c2bd-034a-b1af, GHSA-3rrw-pv9w-qgch, JLSEC-2025-75, MGASA-2022-0177, OESA-2022-1658, RHSA-2022:5250, RHSA-2022:5317, RLSA-2022:5250, RLSA-2022:5317, UBUNTU-CVE-2022-29824, openSUSE-SU-2024:12043-1

## What is CVE-2022-29824?

CVE-2022-29824 is a medium-severity vulnerability in Debian Debian Linux, published on 3 May 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

In libxml2 before 2.9.14, several buffer handling functions in buf.c (xmlBuf*) and tree.c (xmlBuffer*) don't check for integer overflows. This can result in out-of-bounds memory writes. Exploitation requires a victim to open a crafted, multi-gigabyte XML file. Other software using libxml2's buffer functions, for example libxslt through 1.1.35, is affected as well.

Weakness: CWE-190 (Integer Overflow or Wraparound)

## Which versions are affected by CVE-2022-29824?

It affects 19 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libxml2-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.9.7-13.el8_6.1 |
| `libxml2-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.9.7-13.el8_6.1 |
| `libxml2-devel` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.9.7-13.el8_6.1 |
| `python3-libxml2-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:2.9.7-13.el8_6.1 |
| `libxml2` | Red Hat:enterprise_linux:8::baseos | All versions | 0:2.9.7-13.el8_6.1 |
| `libxml2-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:2.9.7-13.el8_6.1 |
| `libxml2-debugsource` | Red Hat:enterprise_linux:8::baseos | All versions | 0:2.9.7-13.el8_6.1 |
| `python3-libxml2` | Red Hat:enterprise_linux:8::baseos | All versions | 0:2.9.7-13.el8_6.1 |
| `python3-libxml2-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:2.9.7-13.el8_6.1 |
| `libxml2-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.9.13-1.el9_0.1 |
| `libxml2-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.9.13-1.el9_0.1 |
| `libxml2-devel` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.9.13-1.el9_0.1 |
| `python3-libxml2-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:2.9.13-1.el9_0.1 |
| `libxml2` | Red Hat:enterprise_linux:9::baseos | All versions | 0:2.9.13-1.el9_0.1 |
| `libxml2-debuginfo` | Red Hat:enterprise_linux:9::baseos | All versions | 0:2.9.13-1.el9_0.1 |
| `libxml2-debugsource` | Red Hat:enterprise_linux:9::baseos | All versions | 0:2.9.13-1.el9_0.1 |
| `python3-libxml2` | Red Hat:enterprise_linux:9::baseos | All versions | 0:2.9.13-1.el9_0.1 |
| `python3-libxml2-debuginfo` | Red Hat:enterprise_linux:9::baseos | All versions | 0:2.9.13-1.el9_0.1 |
| `libxml2` | Rocky Linux:8 | All versions | 0:2.9.7-13.el8_6.1 |
| `libxml2` | Rocky Linux:9 | All versions | 0:2.9.13-1.el9_0.1 |
| `libxml2` | openSUSE:Tumbleweed | All versions | 2.9.14-1.1 |

Products: Debian Debian Linux, Fedoraproject Fedora, Netapp Active Iq Unified Manager, Netapp Clustered Data Ontap, Netapp Clustered Data Ontap Antivirus Connector, Netapp H300s Firmware, Netapp H410c Firmware, Netapp H410s Firmware, Netapp H500s Firmware, Netapp H700s Firmware, Netapp Manageability Software Development Kit, Netapp Ontap Select Deploy Administration Utility, Netapp Smi-S Provider, Netapp Snapdrive, Netapp Snapmanager, Netapp Solidfire \& Hci Management Node, Oracle Zfs Storage Appliance Kit, Xmlsoft Libxml2, Xmlsoft Libxslt.

## How do I fix CVE-2022-29824?

Upgrade to a fixed version.

## Is CVE-2022-29824 being exploited?

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

## Other vulnerabilities in Debian Debian Linux

- [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild)
- [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild)
- [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild)
- [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-29824 and fix it if it is affected.

What it is: CVE-2022-29824 is a medium-severity vulnerability in Debian Debian Linux, published on 3 May 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-29824 in the wild and no public exploit code.

Affected product: Debian Debian Linux. 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-2022-29824/ (Markdown: https://insights.sbomify.com/CVE-2022-29824/index.md)
```

## Sources

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

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