CVE intelligence and bounded remediation

CVE-2017-12621 — Apache Commons Jelly security vulnerability

Critical CVSS 9.8

During Jelly (xml) file parsing with Apache Xerces, if a custom doctype entity is declared with a "SYSTEM" entity with a URL and that entity is used in the body of the Jelly file, during parser instantiation the parser will attempt to connect to said URL. This could lead to XML External Entity (XXE) attacks in Apache Commons Jelly before 1.0.1.

Severity
Critical
CVSS
9.8 (3.1)
Published
2017-09-28
CISA KEV
Not currently listed
Ecosystem
software/application
Weaknesses
CWE-611

Affected products

  • apache / commons_jelly

Matched remediation archetype

XML external entity and unsafe XML processing

This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.

Check exposure

  • Inventory XML parsers used by APIs, file imports, office or image formats, identity protocols, feeds, and background jobs.
  • Determine whether document type declarations, external entities, XInclude, schemas, or network resolvers are enabled.
  • Map parser filesystem and network access and the sensitivity of documents it processes.

Remediate safely

  • Configure each parser to reject document type declarations and disable external entity, XInclude, and network resolution features.
  • Prefer a data format or hardened parser that does not support external resolution, and apply input size and depth limits.
  • Update affected XML libraries and centralize secure parser construction so callers cannot silently override it.

Authoritative sources

Complete CVE record and remediation plan

The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.