Apache Tomcat: JSESSIONID Cookie missing secure attribute in some configurations
Apache Software Foundation Apache Tomcat
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.tomcat:tomcat-catalina Maven |
|
|
Apache Software Foundation Apache Tomcat
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.tomcat:tomcat-catalina Maven |
|
|
When using the RemoteIpFilter with requests received from a reverse proxy via HTTP that include the X-Forwarded-Proto header set to https, session cookies created by Apache Tomcat 11.0.0-M1 to 11.0.0.-M2, 10.1.0-M1 to 10.1.5, 9.0.0-M1 to 9.0.71 and 8.5.0 to 8.5.85 did not include the secure attribute. This could result in the user agent transmitting the session cookie over an insecure channel.
Older, EOL versions may also be affected.
From the CVE record · apache
When RemoteIpFilter receives an HTTP request through a reverse proxy with X-Forwarded-Proto set to https, affected Tomcat versions may create session cookies without the Secure attribute. The user's browser could then send a session cookie over an insecure channel, where it could be exposed.
Operators of Apache Tomcat or Maven org.apache.tomcat:tomcat-catalina versions 11.0.0-M1 to before 11.0.0-M3, 10.1.0-M1 to before 10.1.6, 9.0.0-M1 to before 9.0.72, or 8.5.0 to before 8.5.86 should check their deployments; older end-of-life versions may also be affected.