# CVE-2007-3385: Apache Tomcat Mishandles Character Sequence in Cookies > Improper cookie handling in Apache Tomcat allows remote attackers to leak session IDs and hijack user sessions. - **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:P/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 14 Aug 2007 - **Updated:** 7 Aug 2024 - **Also known as:** GHSA-6j8f-66vh-39mj ## What is CVE-2007-3385? CVE-2007-3385 is a medium-severity vulnerability in Apache Tomcat, published on 14 Aug 2007. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official 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. Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) ## Which versions are affected by CVE-2007-3385? 10 open source packages ship an affected version, including org.apache.tomcat:tomcat. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.apache.tomcat:tomcat` | Maven | From 3.3.0 to 3.3.2 | None | | `org.apache.tomcat:tomcat` | Maven | From 3.3.0 to 3.3.2 | None | | `org.apache.tomcat:tomcat` | Maven | From 4.1.0 to 4.1.36 | None | | `org.apache.tomcat:tomcat` | Maven | From 4.1.0 to 4.1.36 | None | | `org.apache.tomcat:tomcat` | Maven | From 5.0.0 to 5.0.30 | None | | `org.apache.tomcat:tomcat` | Maven | From 5.0.0 to 5.0.30 | None | | `org.apache.tomcat:tomcat` | Maven | From 5.5.0 to 5.5.24 | None | | `org.apache.tomcat:tomcat` | Maven | From 5.5.0 to 5.5.24 | None | | `org.apache.tomcat:tomcat` | Maven | From 6.0.0 to 6.0.13 | None | | `org.apache.tomcat:tomcat` | Maven | From 6.0.0 to 6.0.13 | None | Products: Apache Tomcat. ## How do I fix CVE-2007-3385? Upgrade to a fixed version. ## Is CVE-2007-3385 being exploited? There is no known exploitation of CVE-2007-3385 in the wild and no public exploit code. ## Other vulnerabilities in Apache Tomcat - [CVE-2025-24813](https://insights.sbomify.com/CVE-2025-24813/): Apache Tomcat Path Equivalence (critical 10.0, exploited in the wild) - [CVE-2016-8735](https://insights.sbomify.com/CVE-2016-8735/): Apache Tomcat Remote Code Execution (critical 9.8, exploited in the wild) - [CVE-2017-12617](https://insights.sbomify.com/CVE-2017-12617/): Apache Tomcat Remote Code Execution (high 8.1, exploited in the wild) - [CVE-2017-12615](https://insights.sbomify.com/CVE-2017-12615/): Apache Tomcat on Windows Remote Code Execution (high 8.1, exploited in the wild) - [CVE-2026-34486](https://insights.sbomify.com/CVE-2026-34486/): Apache Tomcat Missing Encryption of Sensitive Data (high 7.5, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2007-3385 and fix it if it is affected. What it is: CVE-2007-3385 is a medium-severity vulnerability in Apache Tomcat, published on 14 Aug 2007. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2007-3385 in the wild and no public exploit code. Affected packages and fixed versions: - org.apache.tomcat:tomcat (Maven): affected from 3.3.0 up to 3.3.2; no fix listed - org.apache.tomcat:tomcat (Maven): affected from 3.3.0 up to 3.3.2; no fix listed - org.apache.tomcat:tomcat (Maven): affected from 4.1.0 up to 4.1.36; no fix listed - org.apache.tomcat:tomcat (Maven): affected from 4.1.0 up to 4.1.36; no fix listed - org.apache.tomcat:tomcat (Maven): affected from 5.0.0 up to 5.0.30; no fix listed - org.apache.tomcat:tomcat (Maven): affected from 5.0.0 up to 5.0.30; no fix listed - org.apache.tomcat:tomcat (Maven): affected from 5.5.0 up to 5.5.24; no fix listed - org.apache.tomcat:tomcat (Maven): affected from 5.5.0 up to 5.5.24; no fix listed - org.apache.tomcat:tomcat (Maven): affected from 6.0.0 up to 6.0.13; no fix listed - org.apache.tomcat:tomcat (Maven): affected from 6.0.0 up to 6.0.13; no fix listed Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2007-3385/ (Markdown: https://insights.sbomify.com/CVE-2007-3385/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2007-3385 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2007-3385 - OSV: https://osv.dev/vulnerability/CVE-2007-3385 --- From sbomify Insights: https://insights.sbomify.com/CVE-2007-3385/ Summaries are generated and may contain mistakes; the official description above is the record.