CVE-2014-3623: Apache WSS4J before 1.6.17 and 2.x before 2.0.2, as used in Apache CXF 2.7.x before 2.7.13 and 3.0.x before 3.0.2, when using…
Noroxi assessment
Priority: Monitor (action score 23/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 9.2% (FIRST EPSS); higher than 95.4% of all records.
- No special conditions are required; it is repeatable.
- Fixed version: org.apache.ws.security:wss4j (Maven) 1.6.17; org.apache.wss4j:wss4j-ws-security-dom (Maven) 2.0.2; apache-cxf (Red Hat:jboss_enterprise_application_platform:6::el5) 0:2.7.12-1.SP1_redhat_5.1.ep6.el5.
Low priority for now. Upgrade to org.apache.ws.security:wss4j (Maven) 1.6.17; org.apache.wss4j:wss4j-ws-security-dom (Maven) 2.0.2; apache-cxf (Red Hat:jboss_enterprise_application_platform:6::el5) 0:2.7.12-1.SP1_redhat_5.1.ep6.el5 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Apache WSS4J before 1.6.17 and 2.x before 2.0.2, as used in Apache CXF 2.7.x before 2.7.13 and 3.0.x before 3.0.2, when using TransportBinding, does not properly enforce the SAML SubjectConfirmation method security semantics, which allows remote attackers to conduct spoofing attacks via unspecified vectors.
- Published
- Oct 30, 2014
- Updated
- Jun 16, 2026
- EPSS
- 9.2% · 95th percentile
- CWE
- CWE-287
Report tools
Action score
23
Low priority for now.
- CVSS
- 20 / 40 · 5.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 3 / 30 · 9.2%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- apache cxf2.7.0 and later · up to 2.7.13 inclusive
- apache cxf3.0.0 and later · before 3.0.2
- apache wss4jbefore 1.6.17
- apache wss4j2.0.0 and later · before 2.0.2
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Maven | org.apache.ws.security:wss4j | before 1.6.17 | 1.6.17 |
| Maven | org.apache.wss4j:wss4j-ws-security-dom | from 2.0.0 · before 2.0.2 | 2.0.2 |
| Red Hat:jboss_enterprise_application_platform:6::el5 | apache-cxf | before 0:2.7.12-1.SP1_redhat_5.1.ep6.el5 | 0:2.7.12-1.SP1_redhat_5.1.ep6.el5 |
| Red Hat:jboss_enterprise_application_platform:6::el5 | wss4j | before 0:1.6.16-2.redhat_3.1.ep6.el5 | 0:1.6.16-2.redhat_3.1.ep6.el5 |
| Red Hat:jboss_enterprise_application_platform:6::el6 | apache-cxf | before 0:2.7.12-1.SP1_redhat_5.1.ep6.el6 | 0:2.7.12-1.SP1_redhat_5.1.ep6.el6 |
| Red Hat:jboss_enterprise_application_platform:6::el6 | wss4j | before 0:1.6.16-2.redhat_3.1.ep6.el6 | 0:1.6.16-2.redhat_3.1.ep6.el6 |
| Red Hat:jboss_enterprise_application_platform:6::el7 | apache-cxf | before 0:2.7.12-1.SP1_redhat_5.1.ep6.el7 | 0:2.7.12-1.SP1_redhat_5.1.ep6.el7 |
| Red Hat:jboss_enterprise_application_platform:6::el7 | wss4j | before 0:1.6.16-2.redhat_3.1.ep6.el7 | 0:1.6.16-2.redhat_3.1.ep6.el7 |
Same product
apache: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-88920Apache WSS4J: SAML Sender-Vouches Authentication Bypass39Monitor
- CVE-2026-89238Apache WSS4J: WSS4J EncryptedHeader child confusion causing wrong protected-header selection36Monitor
- CVE-2026-87830Apache WSS4J: Streaming WS-SecurityPolicy validation may skip element-protection checks.36Monitor
Published before and after this one in the same product
- Later →CVE-2015-0227Feb 12, 2015 · Apache WSS4J before 1.6.17 and 2.x before 2.0.2 allows remote attackers to bypass the requireSignedEncryptedDataElements configuration via…22Monitor
- Later →CVE-2015-0226Oct 30, 2017 · Apache WSS4J before 1.6.17 and 2.0.x before 2.0.2 improperly leaks information about decryption failures when decrypting an encrypted key…32Monitor
- Later →CVE-2026-85532Sep 30, 2026 · Apache WSS4J: Insufficient Validation of Derived-Key Parameters30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Maven:org.apache.ws.security:wss4j | 1.6.17 | Package registry (OSV) |
| Maven:org.apache.wss4j:wss4j-ws-security-dom | 2.0.2 | Package registry (OSV) |
| red hat:apache-cxf | 0:2.7.12-1.SP1_redhat_5.1.ep6.el5 · Red Hat:jboss_enterprise_application_platform:6::el5 | Package registry (OSV) |
| red hat:wss4j | 0:1.6.16-2.redhat_3.1.ep6.el5 · Red Hat:jboss_enterprise_application_platform:6::el5 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- P · data or configuration can be modified
- Availability
- none
- Attack complexity
- Low
- Confidentiality impact
- None
- Integrity impact
- P
- Availability impact
- None
Weakness class (CWE)
CWE-287 · Improper AuthenticationCVSS vector
AV:N/AC:L/Au:N/C:N/I:P/A:N
nvd-primary
Root cause
Authentication is added route by route instead of being enforced in one place. When a route added later bypasses the shared middleware, the session check never runs for it.
The bug in code
The whole CWE-287 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
app.use("/admin", requireSession, adminRouter);
// Route added later skips the middleware
app.post("/admin-api/config", updateConfig);Fixed
const admin = express.Router();
admin.use(requireSession, requireRole("admin"));
admin.post("/config", updateConfig);
app.use("/admin", admin);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Authentication AbuseCAPEC-114Medium
- Authentication BypassCAPEC-115Medium
- Identity SpoofingCAPEC-151likelihood: Medium · Medium
- Fake the Source of DataCAPEC-194Medium
- Exploiting Trust in ClientCAPEC-22likelihood: High · High
- Utilizing REST's Trust in the System Resource to Obtain Sensitive DataCAPEC-57likelihood: Medium · Very High
- Session HijackingCAPEC-593likelihood: High · Very High
- Token ImpersonationCAPEC-633Medium
ATT&CK techniques
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (14 more)Show less
- rhn.redhat.com/errata/RHSA-2015-0675.html
- rhn.redhat.com/errata/RHSA-2015-0850.html
- rhn.redhat.com/errata/RHSA-2015-0851.html
- seclists.org/oss-sec/2014/q4/437
- secunia.com/advisories/61909
- www.securityfocus.com/bid/70736
- exchange.xforce.ibmcloud.com/vulnerabilities/97754
- issues.apache.org/jira/browse/WSS-511
- lists.apache.org/thread.html/r36e44ffc1a9b365327df62cdfaabe85b9a5637de102cea07d79b2dbf%40%3Ccommits.cxf.apache.org%3E
- lists.apache.org/thread.html/rc774278135816e7afc943dc9fc78eb0764f2c84a2b96470a0187315c%40%3Ccommits.cxf.apache.org%3E
- lists.apache.org/thread.html/rd49aabd984ed540c8ff7916d4d79405f3fa311d2fdbcf9ed307839a6%40%3Ccommits.cxf.apache.org%3E
- lists.apache.org/thread.html/rec7160382badd3ef4ad017a22f64a266c7188b9ba71394f0d321e2d4%40%3Ccommits.cxf.apache.org%3E
- lists.apache.org/thread.html/rfb87e0bf3995e7d560afeed750fac9329ff5f1ad49da365129b7f89e%40%3Ccommits.cxf.apache.org%3E
- lists.apache.org/thread.html/rff42cfa5e7d75b7c1af0e37589140a8f1999e578a75738740b244bd4%40%3Ccommits.cxf.apache.org%3E
Vendor advisories and official records. Exploit/PoC links are deliberately left out.