CVE-2023-34624 — htmlcleaner
HIGHCVE-2023-34624 is a high-severity (CVSS 7.5) Out-of-bounds Write vulnerability in net.sourceforge.htmlcleaner:htmlcleaner. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for net.sourceforge.htmlcleaner:htmlcleaner — see the affected versions and patch details below.
htmlcleaner vulnerable to stack exhaustion
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
net.sourceforge.htmlcleaner:htmlcleanerReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
An issue was discovered htmlcleaner thru = 2.28 allows attackers to cause a denial of service or other unspecified impacts via crafted object that uses cyclic dependencies.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | net.sourceforge.htmlcleaner:htmlcleaner | all versions | 2.29net.sourceforge.htmlcleaner:htmlcleaner:2.29 |
Affected Products
htmlcleanerhtmlcleaner_projectResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for net.sourceforge.htmlcleaner:htmlcleaner, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update net.sourceforge.htmlcleaner:htmlcleaner to 2.29 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-34624 is resolved across your whole dependency graph.
Workarounds
Constrain what reaches the vulnerable code: limit the size and shape of untrusted input, isolate the affected component in a sandboxed or least-privileged process, and enable the platform's memory-safety mitigations (ASLR, stack protector, hardened allocator) so an out-of-bounds access is more likely to fail closed than to be exploitable.
Frequently Asked Questions
Is CVE-2023-34624 in your dependencies?
Find it across Maven, including transitive dependencies.