Miggo Logo

CVE-2014-3623:
Improper Authentication in Apache WSS4J

5

CVSS Score

Basic Information

EPSS Score
0.80889%
Published
5/13/2022
Updated
2/2/2023
KEV Status
No
Technology
TechnologyJava

Technical Details

CVSS Vector
AV:N/AC:L/Au:N/C:N/I:P/A:N
Package NameEcosystemVulnerable VersionsFirst Patched Version
org.apache.ws.security:wss4jmaven< 1.6.171.6.17
org.apache.wss4j:wss4j-ws-security-dommaven>= 2.0.0, < 2.0.22.0.2

Vulnerability Intelligence
Miggo AIMiggo AI

Miggo AIRoot Cause Analysis

The vulnerability stems from missing enforcement of SAML SubjectConfirmation semantics in validation logic. The JIRA ticket WSS-511 explicitly shows the fix added a boolean flag to SAML validators to require standard confirmation methods. The vulnerable functions are the SubjectConfirmation validation methods in both SAML1 and SAML2 validators that lacked this enforcement check prior to versions 1.6.17/2.0.2. These functions would appear in stack traces when processing SAML assertions with improper confirmation methods.

Vulnerable functions

Only Mi**o us*rs **n s** t*is s**tion

WAF Protection Rules

WAF Rule

*p**** WSS*J ***or* *.*.** *n* *.x ***or* *.*.*, *s us** in *p**** *X* *.*.x ***or* *.*.** *n* *.*.x ***or* *.*.*, w**n usin* Tr*nsport*in*in*, *o*s not prop*rly *n*or** t** S*ML Su*j**t*on*irm*tion m*t*o* s**urity s*m*nti*s, w*i** *llows r*mot* *tt*

Reasoning

T** vuln*r**ility st*ms *rom missin* *n*or**m*nt o* S*ML Su*j**t*on*irm*tion s*m*nti*s in v*li**tion lo*i*. T** JIR* ti*k*t WSS-*** *xpli*itly s*ows t** *ix ***** * *ool**n *l** to S*ML v*li**tors to r*quir* st*n**r* *on*irm*tion m*t*o*s. T** vuln*r*