Skip to content
Fencer Intel
high 7.5

CVE-2019-12401 json

Apache Solr vulnerable to XML Bomb

published 7y ago modified 4mo ago also GHSA-jq2w-w7v2-69q5 , EUVD-2022-4413

cvss
7.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
8.5%
EPSS 8.5% chance of exploitation in 30 days, percentile 95%
public exploits
0
none known

Summary

Solr versions 1.3.0 to 1.4.1, 3.1.0 to 3.6.2 and 4.0.0 to 4.10.4 are vulnerable to an XML resource consumption attack (a.k.a. Lol Bomb) via it’s update handler.?By leveraging XML DOCTYPE and ENTITY type elements, the attacker can create a pattern that will expand when the server parses the XML causing OOMs.

Patch / fix

  • maven org.apache.solr:solr-core 5.0.0

Is CVE-2019-12401 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2019-12401 updated cvss 7.5

solr: XML resource consumption attack via update handler

  • Red Hat JBoss Data Virtualization 6 solr-core Red Hat JBoss Enterprise Application Platform 6 solr-core
    affected: no fix planned “Out of support scope”
  • Red Hat JBoss Fuse 6 solr-core Red Hat JBoss Fuse Service Works 6 solr-core
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

8.55% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/DrunkenShells/Disclosures/tree/master/CVE-2019-12401-XML%20Bomb-Apache%20Solr referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:N/A:P
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
maven org.apache.solr:solr-core
<5.0.0
5.0.0

Affected products

  • Apache Solr

Classification

Weakness
  • CWE-776 Improper Restriction of Recursive Entity References in DTDs

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.