org.apache.santuario:xmlsec vulnerabilities
Apache XML Security for Java supports XML-Signature Syntax and Processing, W3C Recommendation 12 February 2002, and XML Encryption Syntax and Processing, W3C Recommendation 10 December 2002. Since version 1.4, the library supports the standard Java API JSR-105: XML Digital Signature APIs.
- Registry
- Maven
- Latest
- 4.0.4
- License
- Apache-2.0
8 known advisories
The latest version, 4.0.4, is not affected by any of them. Projects on older versions may be.
mvn versions:use-dep-version -Dincludes=org.apache.santuario:xmlsec -DdepVersion=4.0.4 -DforceVersion=trueIs your project on an affected org.apache.santuario:xmlsec?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for org.apache.santuario:xmlsec
Apache Santuario - XML Security for Java are vulnerable to private key disclosure
- Affected
- >=2.3.0 <2.3.4 · <2.2.6 · >=3.0.0 <3.0.3
- Fixed in
- 2.2.6, 2.3.4, 3.0.3
Apache XML Security For Java vulnerable to Infinite Loop
- Affected
- >=1.4.0 <1.4.8 · >=1.5.0 <1.5.3
- Fixed in
- 1.4.8, 1.5.3
Inefficient Algorithmic Complexity in Apache Santuario XML Security
- Affected
- >=1.4.0 <1.4.8 · >=1.5.0 <1.5.5
- Fixed in
- 1.4.8, 1.5.5
Improper Input Validation in Apache Santuario XML Security
- Affected
- <1.5.6
- Fixed in
- 1.5.6
Improper Input Validation in Apache Santuario XML Security
- Affected
- >=2.0.0 <2.0.3
- Fixed in
- 2.0.3
Apache XML Security For Java vulnerable to authentication bypass by HMAC truncation
- Affected
- >=1.4.0 <1.4.3
- Fixed in
- 1.4.3
Exposure of Sensitive Information to an Unauthorized Actor in Apache Santuario
- Affected
- >=2.2.0 <2.2.3 · <2.1.7
- Fixed in
- 2.1.7, 2.2.3
Improper input validation in Apache Santuario XML Security for Java
- Affected
- >=2.0.3 <2.1.4
- Fixed in
- 2.1.4
Is your org.apache.santuario:xmlsec version vulnerable?
- org.apache.santuario:xmlsec 4.0No known advisories in 4.0.4
- org.apache.santuario:xmlsec 3.0No known advisories in 3.0.6
- org.apache.santuario:xmlsec 2.3No known advisories in 2.3.5
- org.apache.santuario:xmlsec 2.2No known advisories in 2.2.6
- org.apache.santuario:xmlsec 2.11 advisory in 2.1.8
- org.apache.santuario:xmlsec 2.03 advisories in 2.0.10
Which of your client projects still run an old org.apache.santuario:xmlsec?
NPMscan reads the pom.xml, build.gradle and gradle.lockfile in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other Maven packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Maven registry.