How severe is CVE-2011-2204?

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

Which packages are affected by CVE-2011-2204?

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

How do I fix CVE-2011-2204?

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

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

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2011-2204?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2011-2204 can be triaged on real exposure rather than presence alone.

Is CVE-2011-2204 actively exploited in the wild?

No public exploit code has been indexed for CVE-2011-2204 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-2011-2204?

CVE-2011-2204 has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 50th 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-2011-2204?

CVE-2011-2204 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-2011-2204 published, and has it been updated?

CVE-2011-2204 was published on May 14, 2022 and was last updated on February 21, 2024. 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-2011-2204 — tomcat

Fix: apache/tomcat@763a56b

CVE-2011-2204 is a Information Exposure vulnerability in org.apache.tomcat:tomcat. A fix is available for org.apache.tomcat:tomcat — see the affected versions and patch details below.

Insertion of Sensitive Information into Log File in Apache Tomcat

Published

May 14, 2022

Updated

Feb 21, 2024

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs50th percentile — riskier than 50% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

3 pkgs affected

☕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

This issue was fixed in Apache Tomcat 7.0.17 but the release votes for the 7.0.17 and 7.0.18 release candidates did not pass. Therefore, users must download 7.0.19 to obtain a version that includes a fix.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.tomcat:tomcat`	≥ 5.5.0&&< 5.5.34	5.5.34`org.apache.tomcat:tomcat:5.5.34`
☕Maven	`org.apache.tomcat:tomcat`	≥ 6.0.0&&< 6.0.33	6.0.33`org.apache.tomcat:tomcat:6.0.33`
☕Maven	`org.apache.tomcat:tomcat`	≥ 7.0.0&&< 7.0.19	7.0.19`org.apache.tomcat:tomcat:7.0.19`

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 5.5.34 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2011-2204 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2011-2204 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2011-2204. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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

The Red Hat Security Response Team has rated this issue as having low security impact, a future update may address this flaw.

Product	Fixed in	Advisory
Red Hat Enterprise Linux 5	`tomcat5-0:5.5.23-0jpp.22.el5_7`	RHSA-2011:1845
Red Hat Enterprise Linux 6	`tomcat6-0:6.0.24-35.el6_1`	RHSA-2011:1780
Red Hat JBoss Enterprise Web Server 1 for RHEL 5	`tomcat5-0:5.5.33-27_patch_07.ep5.el5`	RHSA-2012:0680
Red Hat JBoss Enterprise Web Server 1 for RHEL 5	`tomcat6-0:6.0.32-24_patch_07.ep5.el5`	RHSA-2012:0682
Red Hat JBoss Web Server 1.0	see advisory	RHSA-2012:0679
Red Hat JBoss Web Server 1.0	see advisory	RHSA-2012:0681

Ubuntu

USN-1252-1Ubuntu

Frequently Asked Questions

Apache Tomcat 5.5.x before 5.5.34, 6.x before 6.0.33, and 7.x before 7.0.19, when the MemoryUserDatabase is used, creates log entries containing passwords upon encountering errors in JMX user creation, which allows local users to obtain sensitive information by reading a log file. This issue was fixed in Apache Tomcat 7.0.17 but the release votes for the 7.0.17 and 7.0.18 release candidates did not pass. Therefore, users must download 7.0.19 to obtain a version that includes a fix.

O3 Security · Impact-Aware SCA

Is CVE-2011-2204 in your dependencies?

O3 Security finds CVE-2011-2204 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works