CVE-2009-0781: XSS

Published Mar 6, 2009
·
Updated

Cross-site scripting (XSS) vulnerability in jsp/cal/cal2.jsp in the calendar application in the examples web application in Apache Tomcat 4.1.0 through 4.1.39, 5.5.0 through 5.5.27, and 6.0.0 through 6.0.18 allows remote attackers to inject arbitrary web script or HTML via the time parameter, related to "invalid HTML."

Other sources

Quoting the upstream advisory:

The calendar application in the examples contains invalid HTML which renders the XSS protection for the time parameter ineffective. An attacker can therefore perform an XSS attack using the time attribute.

Mitigation: 6.0.x users should do one of the following: - remove the examples web application - apply this patch http://svn.apache.org/viewvc?rev=750924&view=rev - upgrade to 6.0.19 when released 5.5.x users should do one of the following: - remove the examples web application - apply this patch http://svn.apache.org/viewvc?rev=750928&view=rev - upgrade to 5.5.28 when released 4.1.x users should do one of the following: - remove the examples web application - apply this patch http://svn.apache.org/viewvc?rev=750927&view=rev - upgrade to 4.1.40 when released

Example: http://localhost:8080/examples/jsp/cal/cal2.jsp?time=8am%20STYLE=xss:e//xpression(try{a=firstTime}catch(e){firstTime=1;alert('XSS')});

Credit: This issue was discovered by Deniz Cevik.

References: http://tomcat.apache.org/security.html http://tomcat.apache.org/security-6.html http://tomcat.apache.org/security-5.html

Red Hat

Affected Software

86 affected componentsFixes available
redhat/tomcat5<0:5.5.23-0jpp.7.el5_3.2
0:5.5.23-0jpp.7.el5_3.2
Apache Tomcat=4.1.0
Apache Tomcat=4.1.1
Apache Tomcat=4.1.2
Apache Tomcat=4.1.3
Apache Tomcat=4.1.3-beta
Apache Tomcat=4.1.4
Apache Tomcat=4.1.5
Apache Tomcat=4.1.6
Apache Tomcat=4.1.7
Apache Tomcat=4.1.8
Apache Tomcat=4.1.9
Apache Tomcat=4.1.9-beta
Apache Tomcat=4.1.10
Apache Tomcat=4.1.11
Apache Tomcat=4.1.12
Apache Tomcat=4.1.13
Apache Tomcat=4.1.14
Apache Tomcat=4.1.15
Apache Tomcat=4.1.16
Apache Tomcat=4.1.17
Apache Tomcat=4.1.18
Apache Tomcat=4.1.19
Apache Tomcat=4.1.20
Apache Tomcat=4.1.21
Apache Tomcat=4.1.22
Apache Tomcat=4.1.23
Apache Tomcat=4.1.24
Apache Tomcat=4.1.25
Apache Tomcat=4.1.26
Apache Tomcat=4.1.27
Apache Tomcat=4.1.28
Apache Tomcat=4.1.29
Apache Tomcat=4.1.30
Apache Tomcat=4.1.31
Apache Tomcat=4.1.32
Apache Tomcat=4.1.33
Apache Tomcat=4.1.34
Apache Tomcat=4.1.35
Apache Tomcat=4.1.36
Apache Tomcat=4.1.37
Apache Tomcat=5.5.0
Apache Tomcat=5.5.1
Apache Tomcat=5.5.2
Apache Tomcat=5.5.3
Apache Tomcat=5.5.4
Apache Tomcat=5.5.5
Apache Tomcat=5.5.6
Apache Tomcat=5.5.7
Apache Tomcat=5.5.8
Apache Tomcat=5.5.9
Apache Tomcat=5.5.10
Apache Tomcat=5.5.11
Apache Tomcat=5.5.12
Apache Tomcat=5.5.13
Apache Tomcat=5.5.14
Apache Tomcat=5.5.15
Apache Tomcat=5.5.16
Apache Tomcat=5.5.17
Apache Tomcat=5.5.18
Apache Tomcat=5.5.19
Apache Tomcat=5.5.20
Apache Tomcat=5.5.21
Apache Tomcat=5.5.22
Apache Tomcat=5.5.23
Apache Tomcat=5.5.24
Apache Tomcat=5.5.25
Apache Tomcat=5.5.26
Apache Tomcat=6.0
Apache Tomcat=6.0.0
Apache Tomcat=6.0.1
Apache Tomcat=6.0.2
Apache Tomcat=6.0.3
Apache Tomcat=6.0.4
Apache Tomcat=6.0.5
Apache Tomcat=6.0.6
Apache Tomcat=6.0.7
Apache Tomcat=6.0.8
Apache Tomcat=6.0.9
Apache Tomcat=6.0.10
Apache Tomcat=6.0.11
Apache Tomcat=6.0.12
Apache Tomcat=6.0.13
Apache Tomcat=6.0.14
Apache Tomcat=6.0.15
Apache Tomcat=6.0.16

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade redhat/tomcat5 to a version that resolves this vulnerability.

    Fixed in 0:5.5.23-0jpp.7.el5_3.2
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Patch rev=750924
  3. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Patch rev=750927
  4. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Patch rev=750928
  5. Upgrade

    Upgrade Apache Tomcat to a version that resolves this vulnerability.

    Fixed in 4.1.40
  6. Upgrade

    Upgrade Apache Tomcat to a version that resolves this vulnerability.

    Fixed in 5.5.28
  7. Upgrade

    Upgrade Apache Tomcat to a version that resolves this vulnerability.

    Fixed in 6.0.19
  8. Remove

    Remove examples web application from your environment.

    remove the examples web application

Event History

Mar 6, 2009
CVE Published
via Red Hat·12:00 AM
Data Sourced
via Red Hat·07:58 PM
DescriptionSeverityAffected Software
Mar 9, 2009
CVE Published
via MITRE·09:00 PM
Data Sourced
via MITRE·09:00 PM
Description
Data Sourced
via NVD·09:30 PM
DescriptionSeverityWeaknessAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is the severity of CVE-2009-0781?

CVE-2009-0781 has a medium severity rating, as it allows remote attackers to exploit cross-site scripting vulnerabilities.

2

How do I fix CVE-2009-0781?

To fix CVE-2009-0781, update your Apache Tomcat installation to version 5.5.28 or later, as these versions have patched the vulnerability.

3

Which versions of Apache Tomcat are affected by CVE-2009-0781?

CVE-2009-0781 affects Apache Tomcat versions 4.1.0 through 4.1.39, 5.5.0 through 5.5.27, and 6.0.0 through 6.0.18.

4

What type of vulnerability is CVE-2009-0781?

CVE-2009-0781 is classified as a cross-site scripting (XSS) vulnerability.

5

Can CVE-2009-0781 be exploited without user interaction?

Yes, CVE-2009-0781 can be exploited by remote attackers without requiring user interaction.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203