CWE-112 Base Draft

Missing XML Validation

This vulnerability occurs when an application processes XML data from an untrusted source without first validating its structure and content against a defined schema.

Definition

What is CWE-112?

This vulnerability occurs when an application processes XML data from an untrusted source without first validating its structure and content against a defined schema.
When you accept XML without schema validation, you're trusting external data to match your code's expectations. Attackers exploit this gap by sending malformed, oversized, or maliciously crafted XML documents that can trigger parsing errors, consume excessive resources, or enable injection attacks. This fundamentally breaks the security assumption that input will be reasonable and well-formed. Consistently validating XML against a strict DTD or XML Schema is a critical first line of defense. While SAST tools can detect missing validation patterns, Plexicus uses AI to analyze your code flow and suggest precise fixes—like implementing schema validation libraries or hardening parser configurations—saving hours of manual security review and helping prevent this common oversight across your entire application portfolio.
Auswirkungen in der Praxis

Real-world CVEs caused by CWE-112

Bisher sind in MITREs Katalog keine öffentlichen CVE-Referenzen mit dieser CWE verknüpft.

Wie Angreifer es ausnutzen

Angreiferpfad Schritt für Schritt

  1. 1

    The following code loads and parses an XML file.

  2. 2

    The XML file is loaded without validating it against a known XML Schema or DTD.

  3. 3

    The following code creates a DocumentBuilder object to be used in building an XML document.

  4. 4

    The DocumentBuilder object does not validate an XML document against a schema, making it possible to create an invalid XML document.

Verwundbares Codebeispiel

Vulnerable Java

The following code loads and parses an XML file.

Verwundbar Java
```
// Read DOM* 
  try {
  ```
  	...
  	DocumentBuilderFactory factory = DocumentBuilderFactory.newInstance();
  	factory.setValidating( false );
  	....
  	c_dom = factory.newDocumentBuilder().parse( xmlFile );
  } catch(Exception ex) {
  	...
  }
Sicheres Codebeispiel

Secure pseudo

Sicher pseudo
// Validate, sanitize, or use a safe API before reaching the sink.
function handleRequest(input) {
  const safe = validateAndEscape(input);
  return executeWithGuards(safe);
}
What changed: the unsafe sink is replaced (or the input is validated/escaped) so the same payload no longer triggers the weakness.
Präventions-Checkliste

How to prevent CWE-112

  • Architecture and Design Always validate XML input against a known XML Schema or DTD. It is not possible for an XML parser to validate all aspects of a document's content because a parser cannot understand the complete semantics of the data. However, a parser can do a complete and thorough job of checking the document's structure and therefore guarantee to the code that processes the document that the content is well-formed.
Erkennungssignale

How to detect CWE-112

Automated Static Analysis High

Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)

Plexicus Auto-Fix

Plexicus erkennt CWE-112 automatisch und öffnet in unter 60 Sekunden einen Fix-PR.

Codex Remedium scannt jeden Commit, identifiziert genau diese Schwachstelle und liefert einen reviewer-ready Pull Request mit dem Patch. Keine Tickets. Keine Hand-offs.

Häufig gestellte Fragen

Frequently asked questions

Was ist CWE-112?

This vulnerability occurs when an application processes XML data from an untrusted source without first validating its structure and content against a defined schema.

Wie gravierend ist CWE-112?

MITRE hat für diese Schwachstelle keine Exploit-Wahrscheinlichkeit veröffentlicht. Behandle sie als mittlere Auswirkung, bis dein Threat Model anderes belegt.

Welche Sprachen oder Plattformen sind von CWE-112 betroffen?

MITRE hat für diese CWE keine betroffenen Plattformen spezifiziert — sie kann in den meisten Anwendungs-Stacks auftreten.

Wie kann ich CWE-112 verhindern?

Always validate XML input against a known XML Schema or DTD. It is not possible for an XML parser to validate all aspects of a document's content because a parser cannot understand the complete semantics of the data. However, a parser can do a complete and thorough job of checking the document's structure and therefore guarantee to the code that processes the document that the content is well-formed.

Wie erkennt und behebt Plexicus CWE-112?

Die SAST-Engine von Plexicus erkennt die Datenfluss-Signatur von CWE-112 bei jedem Commit. Bei einem Treffer öffnet unser Codex-Remedium-Agent einen Fix-PR mit korrigiertem Code, Tests und einer einzeiligen Zusammenfassung für den Reviewer.

Wo erfahre ich mehr über CWE-112?

MITRE veröffentlicht die kanonische Definition unter https://cwe.mitre.org/data/definitions/112.html. Für ergänzende Hinweise kannst du auch die OWASP- und NIST-Dokumentation heranziehen.

Bereit, wenn du es bist

Schluss mit dem Bezahlen pro Entwickler.
Schließ den Kreislauf.

Plexicus ist die KI-native ASPM, die scannt, filtert, fixt, pentestet und erklärt — autonom. Unbegrenzte Entwickler, unbegrenzte Repos, Fair-Use-KI-Aktionen. Echter kostenloser Tarif, €269/mo jährlich, wenn du bereit bist.