# CVE-2017-10672: Use after free in n/a

> Remote attackers can execute arbitrary code via a use-after-free vulnerability in the Perl XML-LibXML module when controlling replaceChild arguments.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 29 Jun 2017
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2017-10672, DLA-1171-1, DSA-4042-1, GHSA-v3c8-h936-vqgh, MGASA-2017-0254, SUSE-SU-2018:0123-1, SUSE-SU-2018:0170-1, UBUNTU-CVE-2017-10672, USN-3494-1

## What is CVE-2017-10672?

CVE-2017-10672 is a critical use after free vulnerability in Debian Debian Linux, published on 29 Jun 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Use-after-free in the XML-LibXML module through 2.0129 for Perl allows remote attackers to execute arbitrary code by controlling the arguments to a replaceChild call.

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2017-10672?

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `perl-XML-LibXML` | SUSE:Linux Enterprise Desktop 12 SP2 | All versions | 2.0019-6.3.5 |
| `perl-XML-LibXML` | SUSE:Linux Enterprise Desktop 12 SP3 | All versions | 2.0019-6.3.5 |
| `perl-XML-LibXML` | SUSE:Linux Enterprise Point of Sale 11 SP3 | All versions | 1.66-3.3.1 |
| `perl-XML-LibXML` | SUSE:Linux Enterprise Server 11 SP3-LTSS | All versions | 1.66-3.3.1 |
| `perl-XML-LibXML` | SUSE:Linux Enterprise Server 11 SP3-TERADATA | All versions | 1.66-3.3.1 |
| `perl-XML-LibXML` | SUSE:Linux Enterprise Server 11 SP4 | All versions | 1.66-3.3.1 |
| `perl-XML-LibXML` | SUSE:Linux Enterprise Server 12 SP2 | All versions | 2.0019-6.3.5 |
| `perl-XML-LibXML` | SUSE:Linux Enterprise Server 12 SP3 | All versions | 2.0019-6.3.5 |
| `perl-XML-LibXML` | SUSE:Linux Enterprise Server for Raspberry Pi 12 SP2 | All versions | 2.0019-6.3.5 |
| `perl-XML-LibXML` | SUSE:Linux Enterprise Server for SAP Applications 11 SP4 | All versions | 1.66-3.3.1 |
| `perl-XML-LibXML` | SUSE:Linux Enterprise Server for SAP Applications 12 SP2 | All versions | 2.0019-6.3.5 |
| `perl-XML-LibXML` | SUSE:Linux Enterprise Server for SAP Applications 12 SP3 | All versions | 2.0019-6.3.5 |

Products: Debian Debian Linux, Xml-Libxml Project Xml-Libxml.

## How do I fix CVE-2017-10672?

Upgrade to a fixed version.

## Is CVE-2017-10672 being exploited?

There is no known exploitation of CVE-2017-10672 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-2017-10672 and fix it if it is affected.

What it is: CVE-2017-10672 is a critical use after free vulnerability in Debian Debian Linux, published on 29 Jun 2017. 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-2017-10672 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-2017-10672/ (Markdown: https://insights.sbomify.com/CVE-2017-10672/index.md)
```

## Sources

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

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