CVE-2007-3385 — tomcat
CVE-2007-3385 is a Information Exposure vulnerability in org.apache.tomcat:tomcat. EPSS puts its 30-day exploitation probability at 16.9% (97th percentile). The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.
Apache Tomcat Mishandles Character Sequence in Cookies
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
Real-World Exposure
org.apache.tomcat:tomcat☕org.apache.tomcat:tomcat☕org.apache.tomcat:tomcat☕org.apache.tomcat:tomcat☕org.apache.tomcat:tomcatReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Apache Tomcat 6.0.0 to 6.0.13, 5.5.0 to 5.5.24, 5.0.0 to 5.0.30, 4.1.0 to 4.1.36, and 3.3 to 3.3.2 does not properly handle the \" character sequence in a cookie value, which might cause sensitive information such as session IDs to be leaked to remote attackers and enable session hijacking attacks.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.tomcat:tomcat | ≥ 6.0.0 | No fix |
| ☕Maven | org.apache.tomcat:tomcat | ≥ 5.5.0 | No fix |
| ☕Maven | org.apache.tomcat:tomcat | ≥ 5.0.0 | No fix |
| ☕Maven | org.apache.tomcat:tomcat | ≥ 4.1.0 | No fix |
| ☕Maven | org.apache.tomcat:tomcat | ≥ 3.3.0 | No fix |
Affected Products
tomcatapacheDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.tomcat:tomcat, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of org.apache.tomcat:tomcat for CVE-2007-3385. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Certificate System 7.3 | ant-0:1.6.5-1jpp_1rh | RHSA-2010:0602 |
| Red Hat Developer Suite V.3 | tomcat5-0:5.5.23-0jpp_11rh | RHSA-2008:0195 |
| Red Hat Enterprise Linux 5 | tomcat5-0:5.5.23-0jpp.3.0.2.el5 | RHSA-2007:0871 |
| Red Hat Network Satellite Server v 4.0 | jakarta-commons-pool-0:1.2-2jpp_2rh | RHSA-2007:1069 |
| Red Hat Network Satellite Server v 4.2 | jabberd-0:2.0s10-3.38.rhn | RHSA-2008:0524 |
| Red Hat Network Satellite Server v 5.0 | jabberd-0:2.0s10-3.38.rhn | RHSA-2008:0261 |
| Red Hat Web Application Stack for RHEL 4 | berkeleydb-0:2.0.90-1jpp.ep1.1 | RHSA-2007:0950 |
| RHAPS Version 2 for RHEL 4 | tomcat5-0:5.5.23-0jpp_4rh.4 | RHSA-2007:0876 |
Frequently Asked Questions
Is CVE-2007-3385 in your dependencies?
Find it across Maven, including transitive dependencies.