CVE-2017-7674: Insufficient Verification of Data Authenticity in Apache Tomcat
Summary
CVE-2017-7674: Insufficient Verification of Data Authenticity in Apache Tomcat. Affects org.apache.tomcat:tomcat across 4 version ranges.
>= 7.0.41, < 7.0.79
>= 8.0.0.RC1, < 8.0.45
>= 8.5.0, < 8.5.16
>= 9.0.0.M1, < 9.0.0.M22
Fixed in 4 releases; the minimum fixed version depends on the release line you run. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
Apache Tomcat is an open-source web server and servlet container that is used to deploy Java-based web applications. It provides a Java HTTP web server environment for running Java code. The CORS Filter in Apache Tomcat versions 7.0.41 to 7.0.78, 8.0.0.RC1 to 8.0.44, 8.5.0 to 8.5.15, and 9.0.0.M1 to 9.0.0.M21 did not add an HTTP Vary header indicating that the response varies depending on Origin. This allowed for client and server-side cache poisoning in certain scenarios.
Vulnerability Detail
The vulnerability in Apache Tomcat allows for client and server-side cache poisoning due to the CORS Filter not adding an HTTP Vary header. This header is necessary to indicate that the response varies depending on the Origin. As a result, an attacker could manipulate the Origin header and poison the cache, leading to potential security breaches and unauthorized access to sensitive information.
How To Fix
Fixed versions by release line
The minimum fixed version depends on the release line you run.
-
>= 7.0.41, < 7.0.797.0.79 -
>= 8.0.0.RC1, < 8.0.458.0.45 -
>= 8.5.0, < 8.5.168.5.16 -
>= 9.0.0.M1, < 9.0.0.M229.0.0.M22
Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →
Workaround
If upgrading to the latest version is not immediately feasible, a workaround can be implemented by manually adding the HTTP Vary header to the response. This can be done by modifying the server configuration or by implementing custom code to add the header. Here is an example of how to add the header using Java code:
response.setHeader("Vary", "Origin");
Please note that this workaround is temporary and it is still recommended to upgrade to the latest secure version as soon as possible.
Conclusion
The vulnerability in Apache Tomcat can be mitigated by upgrading to the latest secure version or by implementing the provided workaround. It is important to stay updated with the latest security patches to protect against potential exploits. For further support and assistance in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for org.apache.tomcat:tomcat →
FAQ
Apache Tomcat is an open-source web server and servlet container that is used to deploy Java-based web applications.
The vulnerability allows for client and server-side cache poisoning, which can lead to security breaches and unauthorized access to sensitive information.
To fix this vulnerability, it is recommended to upgrade to the latest secure version of Apache Tomcat.
Yes, a workaround is available by manually adding the HTTP Vary header to the response.
You can find more information about this vulnerability in the Apache Tomcat security advisories.
References
Related vulnerabilities
Recent vulnerabilities recorded for org.apache.tomcat:tomcat.
