CVE-2011-3375

CVE-2011-3375 is a medium-severity security vulnerability in org.apache.tomcat:tomcat (maven), affecting versions >= 6.0.30, <= 6.0.33. It is fixed in 6.0.35, 7.0.22.

Summary

Apache Tomcat 6.0.30 through 6.0.33 and 7.x before 7.0.22 does not properly perform certain caching and recycling operations involving request objects, which allows remote attackers to obtain unintended read access to IP address and HTTP header information in opportunistic circumstances by reading TCP data.

Impact

Affected versions

org.apache.tomcat:tomcat (>= 6.0.30, <= 6.0.33) org.apache.tomcat:tomcat (>= 7.0, < 7.0.22)

Security releases

org.apache.tomcat:tomcat → 6.0.35 (maven) org.apache.tomcat:tomcat → 7.0.22 (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

See it in your environment

Remediation advice

Upgrade the following packages to resolve this vulnerability:

org.apache.tomcat:tomcat to 6.0.35 or later; org.apache.tomcat:tomcat to 7.0.22 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

  1. What is CVE-2011-3375? CVE-2011-3375 is a medium-severity security vulnerability in org.apache.tomcat:tomcat (maven), affecting versions >= 6.0.30, <= 6.0.33. It is fixed in 6.0.35, 7.0.22.
  2. Which versions of org.apache.tomcat:tomcat are affected by CVE-2011-3375? org.apache.tomcat:tomcat (maven) versions >= 6.0.30, <= 6.0.33 is affected.
  3. Is there a fix for CVE-2011-3375? Yes. CVE-2011-3375 is fixed in 6.0.35, 7.0.22. Upgrade to this version or later.
  4. Is CVE-2011-3375 exploitable, and should I be worried? Whether CVE-2011-3375 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
  5. What actually determines whether CVE-2011-3375 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
  6. How do I fix CVE-2011-3375?
    • Upgrade org.apache.tomcat:tomcat to 6.0.35 or later
    • Upgrade org.apache.tomcat:tomcat to 7.0.22 or later

Other vulnerabilities in org.apache.tomcat:tomcat

CVE-2026-41284CVE-2026-43512CVE-2026-43513CVE-2026-43515CVE-2026-43514

Stop the waste.
Protect your environment with Kodem.