How severe is CVE-2014-0033?

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

Which packages are affected by CVE-2014-0033?

CVE-2014-0033 affects the following packages: org.apache.tomcat:tomcat (Maven). Ecosystems affected: Maven.

How do I fix CVE-2014-0033?

Update org.apache.tomcat:tomcat to 6.0.38 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-0033 is resolved across your whole dependency graph.

How do I detect CVE-2014-0033 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-2014-0033 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2014-0033 actively exploited in the wild?

No public exploit code has been indexed for CVE-2014-0033 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2014-0033?

CVE-2014-0033 has an EPSS (Exploit Prediction Scoring System) score of 9.9%, placing it in the 96th 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 indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2014-0033?

CVE-2014-0033 is classified as Improper Input Validation (CWE-20). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2014-0033 published, and has it been updated?

CVE-2014-0033 was published on May 14, 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-2014-0033 — tomcat

CVE-2014-0033 is a Improper Input Validation vulnerability in org.apache.tomcat:tomcat. A fix is available for org.apache.tomcat:tomcat — see the affected versions and patch details below.

Improper Input Validation in Apache Tomcat

Published

May 14, 2022

Updated

Nov 8, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

9.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs96th percentile — riskier than 96% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

☕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

org/apache/catalina/connector/CoyoteAdapter.java in Apache Tomcat 6.0.33 through 6.0.37 does not consider the disableURLRewriting setting when handling a session ID in a URL, which allows remote attackers to conduct session fixation attacks via a crafted URL.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.tomcat:tomcat`	≥ 6.0.33&&< 6.0.38	6.0.38`org.apache.tomcat:tomcat:6.0.38`

Affected Products

1 product · 5 configurations

Application

tomcatapache

5 versions

6.0.336.0.346.0.356.0.366.0.37

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.
Fix
Update org.apache.tomcat:tomcat to 6.0.38 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-0033 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

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 HatModerate

This issue did not affect JBoss Web, as shipped with various Red Hat JBoss products. The disableURLRewriting property was introduced in Apache Tomcat 6.0.30. All versions of Apache Tomcat prior to 6.0.30 are not affected by this flaw, as the affected feature is not present. Tomcat 6 as shipped with Red Hat JBoss Web…

Product	Fixed in	Advisory
Red Hat JBoss Enterprise Web Server 2 for RHEL 5	`tomcat6-0:6.0.37-19_patch_04.ep6.el5`	RHSA-2014:0525
Red Hat JBoss Web Server 2.0	`tomcat6`	RHSA-2014:0528

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2014-0033 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works