JULI logging component in Apache Tomcat does not restrict certain permissions for web applications
The default catalina.policy in the JULI logging component in Apache Tomcat 5.5.9 through 5.5.25 and 6.0.0 through 6.0.15 does not restrict certain permissions for web applications, which allows attackers to modify logging configuration options and overwrite arbitrary files, as demonstrated by changing the (1) level, (2) directory, and (3) prefix attributes in the `org.apache.juli.FileHandler` handler.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2007-5342US | medium6.4 | — | ||
The default catalina.policy in the JULI logging component in Apache Tomcat 5.5.9 through 5.5.25 and 6.0.0 through 6.0.15 does not restrict certain permissions for web applications,… | ||||
02
references
External citations — patches, advisories, analysis.
- http://lists.apple.com/archives/security-announce/2008/Oct/msg00001.htmlWEB
- http://lists.opensuse.org/opensuse-security-announce/2009-02/msg00002.htmlWEB
- http://marc.info/?l=bugtraq&m=139344343412337&w=2WEB
- http://security.gentoo.org/glsa/glsa-200804-10.xmlWEB
- http://securityreason.com/securityalert/3485WEB
- http://support.apple.com/kb/HT3216WEB
- http://support.avaya.com/elmodocs2/security/ASA-2008-401.htmWEB
- http://svn.apache.org/viewvc?view=rev&revision=606594WEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan