Get ahead
VMware offers training and certification to turbo-charge your progress.
Learn moreWhen validation of an inbound WS-Security header failed, the SOAP fault returned to the sender used the message of the underlying exception as its fault string, telling an unauthenticated sender which check failed and why. Because that message varies with the cause, a sender can also distinguish the failure modes of a message it submitted.
This issue only affects deployments where all the following are true:
AbstractWsSecurityInterceptor subclass, such as Wss4jSecurityInterceptor.EndpointExceptionResolver replaces the fault string built from the validation exception.Fixed versions return the same fault string, Security processing failed, whatever the failure, and log the details instead.
A client relying on the previous fault string to tell failures apart will no longer be able to.
Configure an exceptionResolver to take over building the fault.
Spring Web Services:
| Fix version | Availability |
|---|---|
| 5.0.3.1 | Enterprise Support Only |
| 5.0.4 | OSS |
| 4.1.5 | Enterprise Support Only |
| 4.0.20 | Enterprise Support Only |
| 3.1.10 | Enterprise Support Only |
No further mitigation steps are necessary.
To report a security vulnerability for a project within the Spring portfolio, see the Security Policy