Miggo Logo
Miggo Vulnerability Database
→
CVE-2011-2204

CVE-2011-2204: Insertion of Sensitive Information into Log File in Apache Tomcat

1.9

CVSS Score

Basic Information

CVE ID
CVE-2011-2204
GHSA ID
GHSA-c57p-3v2g-w9rg
EPSS Score
0.23014%
CWE
CWE-200
Published
5/14/2022
Updated
2/21/2024
KEV Status
No
Technology
TechnologyJava

Technical Details

CVSS Vector
AV:L/AC:M/Au:N/C:P/I:N/A:N
Package NameEcosystemVulnerable VersionsFirst Patched Version
org.apache.tomcat:tomcatmaven>= 5.5.0, < 5.5.345.5.34
org.apache.tomcat:tomcatmaven>= 6.0.0, < 6.0.336.0.33
org.apache.tomcat:tomcatmaven>= 7.0.0, < 7.0.197.0.19

Vulnerability Intelligence
Miggo AIMiggo AI

Miggo AIRoot Cause Analysis

The vulnerability stemmed from three key points: 1) JMX error handling in MemoryUserDatabaseMBean logged sensitive user objects, 2) MemoryUser's toString() exposed passwords in serialization, and 3) MemoryUserDatabase.save() persisted these insecure toString() outputs. The commit fixes show direct modifications to these areas: replacing object references with safe identifiers in exceptions, splitting toString() into toXml() with filtering, and updating persistence logic. These changes confirm the original functions were leaking passwords through error logging and XML serialization.

Vulnerable functions

Only Mi**o us*rs **n s** t*is s**tion

WAF Protection Rules

WAF Rule

*p**** Tom**t *.*.x ***or* *.*.**, *.x ***or* *.*.**, *n* *.x ***or* *.*.**, w**n t** M*moryUs*r**t***s* is us**, *r**t*s lo* *ntri*s *ont*inin* p*sswor*s upon *n*ount*rin* *rrors in JMX us*r *r**tion, w*i** *llows lo**l us*rs to o*t*in s*nsitiv* in*

Reasoning

T** vuln*r**ility st*mm** *rom t*r** k*y points: *) JMX *rror **n*lin* in `M*moryUs*r**t***s*M***n` lo**** s*nsitiv* us*r o*j**ts, *) `M*moryUs*r`'s `toStrin*()` *xpos** p*sswor*s in s*ri*liz*tion, *n* *) `M*moryUs*r**t***s*.s*v*()` p*rsist** t**s* i