Santuario XML Security for Java vulnerabilitiesRanked by how likely they are to be used.
Santuario XML Security for Java is made by Apache. We track 6 published vulnerabilities in it, across 57 versions. None of them is on the list of flaws known to be exploited today. If you run Santuario XML Security for Java, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Santuario XML Security for Java vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Santuario XML Security for Java's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Santuario XML Security for Java flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 8.9%CVE-2013-4517Medium
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...
- 7.4%CVE-2021-40690High
All versions of Apache Santuario - XML Security for Java prior to 2.2.3 and 2.1.7 are vulnerable to an issue where the "secureValidation" property is not passed correctly when creating a KeyInfo from a...
- 5.9%CVE-2013-2172Medium
jcp/xml/dsig/internal/dom/DOMCanonicalizationMethod.java in Apache Santuario XML Security for Java 1.4.x before 1.4.8 and 1.5.x before 1.5.5 allows context-dependent attackers to spoof an XML Signature by using the...
- 5.6%CVE-2014-8152Medium
Apache Santuario XML Security for Java 2.0.x before 2.0.3 allows remote attackers to bypass the streaming XML signature protection mechanism via a crafted XML document.
- 1.2%CVE-2023-44483Medium
All versions of Apache Santuario - XML Security for Java prior to 2.2.6, 2.3.4, and 3.0.3, when using the JSR 105 API, are vulnerable to an issue where a private key may be disclosed in log files when generating an...
- 0.8%CVE-2019-12400Medium
In version 2.0.3 Apache Santuario XML Security for Java, a caching mechanism was introduced to speed up creating new XML documents using a static pool of DocumentBuilders.
Running Santuario XML Security for Java? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
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.
- Matched to
- Santuario XML Security for Java on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 6 published vulnerabilities listed under the name Santuario XML Security for Java, across 57 versions.
None of Santuario XML Security for Java's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Santuario XML Security for Java. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.