Cloudanix VulnDB

CVE-2014-0225

High · 8.8

CVSS

8.8

EPSS

1.5%

Published

May 25, 2017

CISA due date

—

Cloudanix analysis

Schedule a fix SSVC: Track

An old flaw in how certain systems handled incoming data files could let attackers steal internal information or reach other systems inside the network if the software has not been updated.

Exploitation
Requires User Interaction
Attacker needs
User Interaction
Complexity
Low
Impact
Data Exposure
Component
Web Framework
Class
XXE
Remediation
Upgrade
Effort
Medium
Patch risk
Low

What it actually does

Failure to disable external entity resolution in DTD declarations when parsing attacker-supplied XML allows out-of-band file retrieval, SSRF, and in some parsers remote code execution via XXE.

Why it matters to the business

Attackers can exfiltrate sensitive configuration files or internal data, pivot into internal systems, or cause service disruption, increasing breach and compliance costs for organizations still running the vulnerable Typo3 Bitnami stack.

How an attack unfolds

An attacker submits a crafted XML document containing a malicious DTD that references external URIs or local files; the vulnerable XML parser resolves those entities and returns or processes the content, enabling data theft or internal network interaction.

How to fix it

Upgrade Typo3 (Bitnami) to version 9.5.17 or later; ensure any bundled XML processing libraries disable external entity resolution and DTDs by default; apply virtual patching or WAF rules as a temporary control if immediate upgrade is not possible.

How to confirm the fix worked

Confirm the installed Typo3 Bitnami package version is 9.5.17 or newer; test the affected endpoints with known-safe XML samples that include DTDs and verify that entity expansion is rejected or logged as an error.

Typical attack path

  1. Identify an endpoint that accepts XML input from untrusted sources.
  2. Craft an XML payload containing a DTD with external entity declarations pointing to file:// or http:// targets.
  3. Submit the payload via the affected input channel.
  4. Observe successful entity expansion that returns file contents or triggers outbound requests.
  5. Exfiltrate retrieved data or chain the access into further internal attacks.

How to detect it

Review web application and XML parser logs for requests containing DOCTYPE, ENTITY, or SYSTEM keywords; inspect outbound connections or file-access attempts triggered by XML processing; correlate unusual XML payloads with successful responses containing internal file contents or error messages indicating entity expansion.

What your security team should do

  • Immediately schedule upgrade of all Typo3 Bitnami instances to 9.5.17+.
  • Add XML input sanitization and disable DTD/external entity processing in any custom XML handlers.
  • Scan historical logs for XML payloads containing DOCTYPE or ENTITY declarations to assess prior exposure.
  • Update vulnerability management tooling to flag any remaining pre-9.5.17 deployments as critical.

The record

When processing user provided XML documents, the Spring Framework 4.0.0 to 4.0.4, 3.0.0 to 3.2.8, and possibly earlier unsupported versions did not disable by default the resolution of URI references in a DTD declaration. This enabled an XXE attack.

Affected packages

Ecosystem Package Introduced Fixed
Maven org.springframework:spring-webmvc 3.0.0 3.2.8
Maven org.springframework:spring-webmvc 4.0.0 4.0.5
Debian:10 libspring-java 0 3.0.6.RELEASE-14
Debian:11 libspring-java 0 3.0.6.RELEASE-14
Debian:12 libspring-java 0 3.0.6.RELEASE-14
Debian:13 libspring-java 0 3.0.6.RELEASE-14
Mageia:4 springframework 0 3.1.4-2.3.mga4
Ubuntu:Pro:14.04:LTS libspring-java 0 3.0.6.RELEASE-13ubuntu0.1~esm1
Ubuntu:Pro:14.04:LTS libspring-java 0 3.0.6.RELEASE-13ubuntu0.1~esm2
Ubuntu:Pro:16.04:LTS libspring-java 0 3.2.13-5ubuntu0.1~esm1
maven org.springframework/spring-oxm 3-alpha0 No fix
maven org.springframework/spring-oxm 4-alpha0 No fix
maven org.springframework/spring-web 3 No fix
maven org.springframework/spring-web 4 No fix
maven org.springframework/spring-webmvc 3.0.0 3.2.8
maven org.springframework/spring-webmvc 4.0.0 4.0.5

Related vulnerabilities