- When applications specify HTTP response headers for servlet applications using Spring Security, there is the possibility that the HTTP Headers will not be written.
- This issue affects Spring Security Servlet applications using lazy (default) writing of HTTP Headers:
from 5.7.0 through 5.7.21, from 5.8.0 through 5.8.23, from 6.3.0 through 6.3.14, from 6.4.0 through 6.4.14, from 6.5.0 through 6.5.8, from 7.0.0 through 7.0.3.
Weakness
The web application does not adequately enforce appropriate authorization on all restricted URLs, scripts, or files.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Spring_security | Vmware | * | 5.7.22 (excluding) |
| Spring_security | Vmware | 5.8.0 (including) | 5.8.24 (excluding) |
| Spring_security | Vmware | 6.3.0 (including) | 6.3.15 (excluding) |
| Spring_security | Vmware | 6.4.0 (including) | 6.4.15 (excluding) |
| Spring_security | Vmware | 6.5.0 (including) | 6.5.9 (excluding) |
| Spring_security | Vmware | 7.0.0 (including) | 7.0.4 (excluding) |
Potential Mitigations
Related Attack Patterns
- https://cwe.mitre.org/data/definitions/127.html
- https://cwe.mitre.org/data/definitions/143.html
- https://cwe.mitre.org/data/definitions/144.html
- https://cwe.mitre.org/data/definitions/668.html
- https://cwe.mitre.org/data/definitions/87.html