Under Some Conditions Spring Security HTTP Headers Are not Written
VMware Spring Security
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.springframework.security:spring-security-web Maven |
|
|
VMware Spring Security
| Product | Affected | Fixed in |
|---|---|---|
| org.springframework.security:spring-security-web Maven |
|
|
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.
From the CVE record · vmware
Spring Security Servlet applications using default lazy writing may fail to write configured HTTP response headers. This can leave responses without those headers. The input does not specify what an attacker can do with the missing headers or whether network access, authentication, or user interaction is required.
Teams running Spring Security Servlet applications should check Maven package org.springframework.security:spring-security-web in the listed affected ranges: through 5.7.14, 5.8.0–5.8.16, 6.0.0–6.3.10, 6.4.0–6.4.13, 6.5.0–6.5.8, or 7.0.0–7.0.3.