CVE-2018-1000632

Vulnerability in dom4j (CVE-2018-1000632)

Summary

Vulnerability in dom4j (CVE-2018-1000632). Data can be tampered with by attackers. Mitigation: upgrade to 2.1.1 or later.

Original description

The description as published by the source.

dom4j version prior to version 2.1.1 contains a CWE-91: XML Injection vulnerability in Class: Element. Methods: addElement, addAttribute that can result in an attacker tampering with XML documents through XML injection. This attack appear to be exploitable via an attacker specifying attributes or elements in the XML document. This vulnerability appears to have been fixed in 2.1.1 or later.

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2018-1000632 has been found in dom4j.
Data can be tampered with by attackers.
What to do: upgrade dom4j to 2.1.1 or later.
If unsure, ask your IT team or search "dom4j CVE-2018-1000632" on the vendor's site.

CVE-2018-1000632 (dom4j)
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 2.1.1 — 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 dom4j.

📍 Affected scope

Check the vendor advisory for the affected versions of dom4j.

🔥 Severity

Severity: ?. Data can be tampered with by attackers.

🔧 How to fix

Update to 2.1.1.

🛡️ 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 'dom4j' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

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

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

Fix status by distribution

Fixed packages published by each distribution for this CVE

Debian DEBIAN-CVE-2018-1000632 dom4j Fixed in: 2.1.1-1