How severe is CVE-2007-3382?

No CVSS score has been assigned to CVE-2007-3382 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2007-3382?

CVE-2007-3382 affects the following packages: org.apache.tomcat:tomcat (Maven), org.apache.tomcat:tomcat (Maven), org.apache.tomcat:tomcat (Maven), org.apache.tomcat:tomcat (Maven), org.apache.tomcat:tomcat (Maven). Ecosystems affected: Maven.

How do I fix CVE-2007-3382?

The records we use list no patched version of org.apache.tomcat:tomcat for CVE-2007-3382. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect CVE-2007-3382 in my Maven dependencies?

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.

How do I mitigate CVE-2007-3382 if there is no patch (or I can't update yet)?

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.

Is CVE-2007-3382 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2007-3382, including 1 documented proof-of-concept exploit on Exploit-DB. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2007-3382?

CVE-2007-3382 has an EPSS (Exploit Prediction Scoring System) score of 37.5%, placing it in the 99th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score warrants monitoring and prompt remediation.

What type of vulnerability is CVE-2007-3382?

CVE-2007-3382 is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2007-3382 published, and has it been updated?

CVE-2007-3382 was published on May 1, 2022 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

CVE-2007-3382 — tomcat

CVE-2007-3382 is a Information Exposure vulnerability in org.apache.tomcat:tomcat. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

Apache Tomcat treats single quotes as delimiters in cookies

Published

May 1, 2022

Updated

Nov 8, 2023

Affected

5 pkgs

Patched

See advisory

Exploits

1 known

Exploitation data as of Nov 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

37.5%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs99th percentile — riskier than 99% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

5 pkgs affected

☕org.apache.tomcat:tomcat☕org.apache.tomcat:tomcat☕org.apache.tomcat:tomcat☕org.apache.tomcat:tomcat☕org.apache.tomcat:tomcat

Real-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 treats single quotes (') as delimiters in cookies, which might cause sensitive information such as session IDs to be leaked and allow remote attackers to conduct session hijacking attacks.

Affected Packages

5 total

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

1 product · 85 configurations

Application

tomcatapache

84 versions

3.33.3.13.3.1a3.3.24.1.04.1.14.1.24.1.34.1.94.1.104.1.154.1.24

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-30496remotemultiple✓ Verified

Apache Tomcat 6.0.13 - Insecure Cookie Handling Quote Delimiter Session ID Disclosure

by Tomasz Kuczynski · Aug 14, 2007

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

Detect
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-3382. 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.

Red HatLow

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

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 treats single quotes (`'`) as delimiters in cookies, which might cause sensitive information such as session IDs to be leaked and allow remote attackers to conduct session hijacking attacks.

O3 Security · Impact-Aware SCA

Is CVE-2007-3382 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works