# CVE-2013-4517: Improper Input Validation in Apache Santuario XML Security

> Remote attackers can cause denial of service via memory consumption in Apache Santuario XML Security for Java by sending crafted Document Type Definitions.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Jan 2014
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2013-4517, GHSA-4p4w-6h54-g885, MGASA-2014-0558, RHSA-2014:1726, RHSA-2014:1728

## What is CVE-2013-4517?

CVE-2013-4517 is a medium-severity denial of service vulnerability in n/a, published on 11 Jan 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Apache Santuario XML Security for Java before 1.5.6, when applying Transforms, allows remote attackers to cause a denial of service (memory consumption) via crafted Document Type Definitions (DTDs), related to signatures.

Weakness: CWE-399

## Which versions are affected by CVE-2013-4517?

2 open source packages ship an affected version, including org.apache.santuario:xmlsec. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.santuario:xmlsec` | Maven | All versions | 1.5.6 |
| `org.apache.santuario:xmlsec` | Maven | All versions | 1.5.6 |
| `xml-security` | Red Hat:jboss_enterprise_application_platform:5::el4 | All versions | 0:1.5.6-3.ep5.el4 |
| `xml-security` | Red Hat:jboss_enterprise_application_platform:5::el5 | All versions | 0:1.5.6-3.ep5.el5 |
| `xml-security` | Red Hat:jboss_enterprise_application_platform:5::el6 | All versions | 0:1.5.6-3.el6 |
| `xml-security` | Red Hat:jboss_enterprise_web_platform:5::el5 | All versions | 0:1.5.6-3.ep5.el5 |
| `xml-security` | Red Hat:jboss_enterprise_web_platform:5::el6 | All versions | 0:1.5.6-3.el6 |

Products: Apache Santuario Xml Security for Java.

## How do I fix CVE-2013-4517?

Upgrade org.apache.santuario:xmlsec to 1.5.6 or later.

## Is CVE-2013-4517 being exploited?

There is no known exploitation of CVE-2013-4517 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2023-44483](https://insights.sbomify.com/CVE-2023-44483/): Apache Santuario: Private Key disclosure in debug-log output (medium 6.5)
- [CVE-2019-12400](https://insights.sbomify.com/CVE-2019-12400/): Improper input validation in Apache Santuario XML Security for Java (medium 5.5)
- [CVE-2014-8152](https://insights.sbomify.com/CVE-2014-8152/): Improper Input Validation in Apache Santuario XML Security (medium 5.0)
- [CVE-2013-2172](https://insights.sbomify.com/CVE-2013-2172/): Inefficient Algorithmic Complexity in Apache Santuario XML Security (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-4517 and fix it if it is affected.

What it is: CVE-2013-4517 is a medium-severity denial of service vulnerability in n/a, published on 11 Jan 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-4517 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.santuario:xmlsec (Maven): affected all versions; fixed in 1.5.6
- org.apache.santuario:xmlsec (Maven): affected all versions; fixed in 1.5.6

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2013-4517/ (Markdown: https://insights.sbomify.com/CVE-2013-4517/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2013-4517
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2013-4517
- OSV: https://osv.dev/vulnerability/CVE-2013-4517

---
From sbomify Insights: https://insights.sbomify.com/CVE-2013-4517/
Summaries are generated and may contain mistakes; the official description above is the record.