This is an automated email from the ASF dual-hosted git repository. robertlazarski pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/axis-axis2-java-rampart.git
commit d7c4463d92ea2389333b9116941727db969ac915 Author: Robert Lazarski <[email protected]> AuthorDate: Fri Nov 13 04:35:04 2026 -1000 Bump WSS4J to 4.0.2, OpenSAML to 5.2.3, Bouncy Castle to 1.87 WSS4J 4.0.2 carries the 2026 CVE fixes for the DOM WS-Security path Rampart uses and is built against OpenSAML 5.2.3, so both move together. Bouncy Castle 1.87 is the current release. Full reactor including the nine policy samples passes; SECURITY.md and AGENTS.md now name the versions actually shipped. Co-Authored-By: Claude Fable 5.1 <[email protected]> --- AGENTS.md | 4 ++-- SECURITY.md | 20 ++++++++++---------- pom.xml | 8 +++++--- 3 files changed, 17 insertions(+), 15 deletions(-) diff --git a/AGENTS.md b/AGENTS.md index 39e03056..832b9705 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -8,7 +8,7 @@ See [SECURITY.md](SECURITY.md) for the full threat model, including: - Roles and trust levels - Security boundaries: what is and is not a security issue - Attack surface by component (signatures, encryption, SAML, Kerberos, UsernameToken) -- Critical dependency versions (WSS4J 4.0.1, OpenSAML 5.2.1) +- Critical dependency versions (WSS4J 4.0.2, OpenSAML 5.2.3) - CVE history context ## High-Priority Scan Areas @@ -26,7 +26,7 @@ Key files: ### 2. Signature Wrapping -Rampart relies on WSS4J 4.0.1 for signature reference validation. Verify +Rampart relies on WSS4J 4.0.2 for signature reference validation. Verify that Rampart's preprocessing in `Axis2Util.getDocumentFromSOAPEnvelope()` (which converts Axiom to DOM and normalizes namespaces) does not create opportunities for signature wrapping attacks. diff --git a/SECURITY.md b/SECURITY.md index a38a3d1c..7662e8be 100644 --- a/SECURITY.md +++ b/SECURITY.md @@ -10,8 +10,8 @@ WS-SecureConversation. Rampart is deployed as an Axis2 module (MAR) that adds inbound and outbound security handlers to the Axis2 message processing pipeline. -Rampart delegates cryptographic operations to Apache WSS4J (4.0.1) and -SAML processing to OpenSAML (5.2.1). It is the security enforcement +Rampart delegates cryptographic operations to Apache WSS4J (4.0.2) and +SAML processing to OpenSAML (5.2.3). It is the security enforcement layer — if Rampart is bypassed or misconfigured, Axis2 services have no message-level security. @@ -95,11 +95,11 @@ RampartEngine.process(MessageContext) Extract WS-Security header | v -WSSecurityEngine (WSS4J 4.0.1) +WSSecurityEngine (WSS4J 4.0.2) - Validate signatures (XML-DSIG via Apache Santuario) - Decrypt encrypted parts (XML-ENC) - Validate UsernameToken (password callback) - - Validate SAML assertions (OpenSAML 5.2.1) + - Validate SAML assertions (OpenSAML 5.2.3) - Validate Kerberos tokens (JDK JAAS/GSS) - Validate timestamps (clock skew tolerance) | @@ -129,9 +129,9 @@ Axis2 Transport-Out Phase | Component | Threats | Mitigations | |-----------|---------|-------------| -| **XML Signature validation** (WSS4J/Santuario) | Signature wrapping; reference manipulation; HMAC truncation | WSS4J 4.0.1 signature reference validation; Santuario's strict reference processing | +| **XML Signature validation** (WSS4J/Santuario) | Signature wrapping; reference manipulation; HMAC truncation | WSS4J 4.0.2 signature reference validation; Santuario's strict reference processing | | **XML Encryption** (WSS4J/Santuario) | Padding oracle; chosen-ciphertext attacks; CBC mode weaknesses | Algorithm suite enforcement; GCM recommended over CBC | -| **SAML assertion parsing** (OpenSAML 5.2.1) | XXE in assertion XML; forged assertions; expired/replayed assertions; issuer spoofing | OpenSAML unmarshalling; assertion signature validation; NotBefore/NotOnOrAfter enforcement; issuer certificate pinning | +| **SAML assertion parsing** (OpenSAML 5.2.3) | XXE in assertion XML; forged assertions; expired/replayed assertions; issuer spoofing | OpenSAML unmarshalling; assertion signature validation; NotBefore/NotOnOrAfter enforcement; issuer certificate pinning | | **SAML2Utils.getSAML2KeyInfo()** | XXE — `DocumentBuilderFactory.newInstance()` without explicit XXE hardening flags | Depends on OpenSAML's `AxiomParserPool` configuration; **review needed** | | **WS-Trust STS (rahas module)** | Token issuance policy bypass; privilege escalation via crafted RequestSecurityToken (RST); DoS against token issuance | `TokenIssuer` implementations must validate RSTs against policy before issuing tokens | | **UsernameToken validation** | Plaintext password interception; weak hashing; brute force | TransportBinding requires HTTPS for plaintext; nonce+created for hashed; callback-based validation | @@ -147,8 +147,8 @@ Axis2 Transport-Out Phase | Dependency | Version | Security Role | |-----------|---------|---------------| -| **WSS4J** | 4.0.1 | Core WS-Security processing — signatures, encryption, token validation | -| **OpenSAML** | 5.2.1 | SAML assertion parsing, validation, and issuance | +| **WSS4J** | 4.0.2 | Core WS-Security processing — signatures, encryption, token validation | +| **OpenSAML** | 5.2.3 | SAML assertion parsing, validation, and issuance | | **Apache Santuario** (xmlsec) | via WSS4J | XML Signature and XML Encryption implementation | | **Bouncy Castle** | runtime dependency | JCE provider for advanced crypto algorithms | @@ -164,9 +164,9 @@ heavily on WSS4J and OpenSAML, which have extensive CVE histories: - **WSS4J CVEs** include signature wrapping (CVE-2011-2487), SOAP Action spoofing, and various XML signature bypass issues. - Rampart 2.0.0 uses WSS4J 4.0.1, which addresses all known issues. + Rampart 2.0.0 uses WSS4J 4.0.2, which addresses all known issues. - **OpenSAML CVEs** include XXE in SAML assertion parsing and assertion - replay. Rampart 2.0.0 uses OpenSAML 5.2.1. + replay. Rampart 2.0.0 uses OpenSAML 5.2.3. The scan should verify that Rampart's integration with these libraries does not reintroduce vulnerabilities that the libraries themselves have diff --git a/pom.xml b/pom.xml index 41dd8d5a..42c617da 100644 --- a/pom.xml +++ b/pom.xml @@ -853,12 +853,14 @@ <axis2.version>2.0.2</axis2.version> <axiom.version>2.0.0</axiom.version> - <wss4j.version>4.0.1</wss4j.version> - <opensaml.version>5.2.2</opensaml.version> + <!-- WSS4J 4.0.2 is built against OpenSAML 5.2.3, xmlsec 4.0.4 and + cryptacular 1.3.0; keep those aligned when bumping wss4j. --> + <wss4j.version>4.0.2</wss4j.version> + <opensaml.version>5.2.3</opensaml.version> <dropwizard.metrics.version>4.2.40</dropwizard.metrics.version> <cryptacular.version>1.3.0</cryptacular.version> - <bcprov.jdk18.version>1.85</bcprov.jdk18.version> + <bcprov.jdk18.version>1.87</bcprov.jdk18.version> <!-- Fail the build if a module expected to have tests suddenly has none (tests deleted or no longer discovered). Surefire reads this property
