Skip to content
Noroxi
NVD / CVE Program· CNA redhat

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…

MediumCVSS 5.0 · v2.0—No exploit Fix available

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

Report tools

JSON

Action score

23

Monitor

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.

Follow CVE-2014-3623

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi 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 help

Affected 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.

VendorProduct
apachewss4j
apachecxf

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.

EcosystemPackageAffected rangeFix
Mavenorg.apache.ws.security:wss4jbefore 1.6.171.6.17
Mavenorg.apache.wss4j:wss4j-ws-security-domfrom 2.0.0 · before 2.0.22.0.2
Red Hat:jboss_enterprise_application_platform:6::el5apache-cxfbefore 0:2.7.12-1.SP1_redhat_5.1.ep6.el50:2.7.12-1.SP1_redhat_5.1.ep6.el5
Red Hat:jboss_enterprise_application_platform:6::el5wss4jbefore 0:1.6.16-2.redhat_3.1.ep6.el50:1.6.16-2.redhat_3.1.ep6.el5
Red Hat:jboss_enterprise_application_platform:6::el6apache-cxfbefore 0:2.7.12-1.SP1_redhat_5.1.ep6.el60:2.7.12-1.SP1_redhat_5.1.ep6.el6
Red Hat:jboss_enterprise_application_platform:6::el6wss4jbefore 0:1.6.16-2.redhat_3.1.ep6.el60:1.6.16-2.redhat_3.1.ep6.el6
Red Hat:jboss_enterprise_application_platform:6::el7apache-cxfbefore 0:2.7.12-1.SP1_redhat_5.1.ep6.el70:2.7.12-1.SP1_redhat_5.1.ep6.el7
Red Hat:jboss_enterprise_application_platform:6::el7wss4jbefore 0:1.6.16-2.redhat_3.1.ep6.el70:1.6.16-2.redhat_3.1.ep6.el7

Other highest-scoring records for the same primary product.

  • CVE-2026-88920Apache WSS4J: SAML Sender-Vouches Authentication Bypass
    39Monitor
  • CVE-2026-89238Apache WSS4J: WSS4J EncryptedHeader child confusion causing wrong protected-header selection
    36Monitor
  • 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 Parameters
    30Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Maven:org.apache.ws.security:wss4j1.6.17Package registry (OSV)
Maven:org.apache.wss4j:wss4j-ws-security-dom2.0.2Package registry (OSV)
red hat:apache-cxf0:2.7.12-1.SP1_redhat_5.1.ep6.el5 · Red Hat:jboss_enterprise_application_platform:6::el5Package registry (OSV)
red hat:wss4j0:1.6.16-2.redhat_3.1.ep6.el5 · Red Hat:jboss_enterprise_application_platform:6::el5Package 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

CVSS 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.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
app.use("/admin", requireSession, adminRouter);
// Route added later skips the middlewareapp.post("/admin-api/config", updateConfig);

Fixed

ts
const admin = express.Router();admin.use(requireSession, requireRole("admin"));
admin.post("/config", updateConfig);app.use("/admin", admin);

References

All records