Improper Authentication in Apache WSS4J
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.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2014-3623US | medium5.0 | — | ||
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 S… | ||||
02
references
External citations — patches, advisories, analysis.
- http://rhn.redhat.com/errata/RHSA-2015-0236.htmlWEB
- http://rhn.redhat.com/errata/RHSA-2015-0675.htmlWEB
- http://rhn.redhat.com/errata/RHSA-2015-0850.htmlWEB
- http://rhn.redhat.com/errata/RHSA-2015-0851.htmlWEB
- http://seclists.org/oss-sec/2014/q4/437WEB
- https://exchange.xforce.ibmcloud.com/vulnerabilities/97754WEB
- https://issues.apache.org/jira/browse/WSS-511WEB
- https://lists.apache.org/thread.html/r36e44ffc1a9b365327df62cdfaabe85b9a5637de102cea07d79b2dbf@%3Ccommits.cxf.apache.org%3EWEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan