LiveActive security incident?Get immediate response
CVE Record

CVE-2021-33813: An XXE issue in SAXBuilder in JDOM through 2.0.6 allows attackers to cause a denial of service via a crafte...

An XXE issue in SAXBuilder in JDOM through 2.0.6 allows attackers to cause a denial of service via a crafted HTTP request.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2021-33813 is an XML parsing flaw in JDOM's SAXBuilder through version 2.0.6. A crafted HTTP request can trigger denial of service. Business urgency depends on whether internet-facing or high-volume services parse untrusted XML using JDOM or bundled copies in products such as Solr or Tika.

Executive priority

Prioritize remediation for internet-facing Java services and critical internal platforms that parse XML. Without evidence of active exploitation or a CVSS score in the bundle, this is not automatically emergency-level, but denial-of-service risk can be material for customer-facing systems.

Technical view

The issue is described as XXE in JDOM SAXBuilder through 2.0.6, with denial-of-service impact. Public references show Linux distribution updates and downstream concern for bundled JDOM in Apache Solr and Apache Tika. The bundle does not provide CVSS, CWE, proof of active exploitation, or detailed fixed-version mapping.

Likely exposure

Exposure is most likely in Java applications or vendor products that parse untrusted XML with JDOM, libjdom1-java, or libjdom2-java. Transitive dependencies and bundled libraries matter, especially where XML parsing is reachable from HTTP requests.

Exploitation context

The source bundle says a crafted HTTP request can cause denial of service. It does not cite CISA KEV listing, active exploitation, public weaponization, or data theft impact. Treat exploitation evidence as incomplete.

Researcher notes

Key gaps are missing CVSS, CWE, exact upstream fixed version details, and exploit-status evidence. Validate reachability, not just package presence: vulnerable JDOM is highest risk when SAXBuilder processes attacker-controlled XML over HTTP.

Mitigation direction

  • Inventory direct and transitive JDOM, libjdom1-java, and libjdom2-java usage.
  • Upgrade JDOM or distribution packages to vendor-confirmed fixed builds.
  • Check bundled JDOM in Solr, Tika, and other Java products.
  • Apply Debian, Fedora, Oracle, or application-vendor security updates where applicable.
  • Review XML parsing exposure on public HTTP request paths.

Validation and detection

  • Search dependency manifests and SBOMs for JDOM versions through 2.0.6.
  • Confirm operating-system packages include relevant Debian or Fedora security updates.
  • Check application bundles for embedded JDOM jars, not only top-level dependencies.
  • Review logs for unusual XML parsing errors or denial-of-service symptoms.
  • Verify internet-facing endpoints do not parse untrusted XML with vulnerable JDOM.
Prepared
Confidence
medium
Sources
10

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2021-33813 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
18Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.