Vulnerability in libxml2 (USN-7302-1)

Summary

vulnerability in libxml2 (USN-7302-1). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to `2.9.1+dfsg1-3ubuntu4.13+esm7` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **USN-7302-1** has been found in libxml2. Risk of unauthorized operations or information disclosure. CVSS score: ?/10. What to do: upgrade libxml2 to **2.9.1+dfsg1-3ubuntu4.13+esm7** or later. If unsure, ask your IT team or search "libxml2 USN-7302-1" on the vendor's site.

USN-7302-1 (libxml2) — Patched: `2.9.1+dfsg1-3ubuntu4.13+esm7` — apply immediately Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs. Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

**A vulnerability** (unclassified) exists in libxml2.

📍 Affected scope

libxml2 — .

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure

🔧 How to fix

Update to **2.9.1+dfsg1-3ubuntu4.13+esm7**.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'libxml2' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response Actions (7 steps)

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
grep -r 'libxml2' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `libxml2` を grep し、稼働しているサービス・バージョンを把握する。
6
Apply patch patch
```
Upgrade libxml2 to 2.9.1+dfsg1-3ubuntu4.13+esm7
```
ステージング環境で 2.9.1+dfsg1-3ubuntu4.13+esm7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
7
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

Ubuntu:Pro:14.04:LTS libxml2

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.9.1+dfsg1-3ubuntu4.13+esm7"}]}]

Ubuntu:Pro:16.04:LTS libxml2

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.9.3+dfsg1-1ubuntu0.7+esm7"}]}]

Ubuntu:Pro:18.04:LTS libxml2

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.9.4+dfsg1-6.1ubuntu1.9+esm2"}]}]

Ubuntu:20.04:LTS libxml2

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.9.10+dfsg-5ubuntu0.20.04.9"}]}]

Ubuntu:22.04:LTS libxml2

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.9.13+dfsg-1ubuntu0.6"}]}]

Ubuntu:24.04:LTS libxml2

[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.9.14+dfsg-1.3ubuntu3.2"}]}]

References

advisory https://ubuntu.com/security/notices/USN-7302-1
report https://ubuntu.com/security/CVE-2022-49043
report https://ubuntu.com/security/CVE-2024-34459
report https://ubuntu.com/security/CVE-2024-56171
report https://ubuntu.com/security/CVE-2025-24928
report https://ubuntu.com/security/CVE-2025-27113