Get ahead
VMware offers training and certification to turbo-charge your progress.
Learn moreA client that sets validateResponse on PayloadValidatingInterceptor did not reject a response that failed schema validation.
The errors were logged and the response was returned to the application anyway, and the rest of the interceptor chain was skipped, including any interceptor declared before the validating one.
This issue only affects deployments where all the following are true:
PayloadValidatingInterceptor with validateResponse set to true.Wss4jSecurityInterceptor validating responses, is declared before that validating interceptor in the client's interceptor list.As Wss4jSecurityInterceptor validates responses by default, a response that failed schema validation therefore reached the application with its WS-Security header never checked.
An attacker able to supply the response can bypass signature and encryption checks by making the payload schema-invalid.
Fixed versions reject such a response with a WebServiceValidationException.
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 |
If you cannot upgrade immediately, either unset validateResponse on the validating interceptor, so that the code path is not reached and WS-Security validation of responses continues to apply, or subclass the interceptor and override handleResponseValidationErrors to throw a WebServiceValidationException.
To report a security vulnerability for a project within the Spring portfolio, see the Security Policy