Skip to content
Fencer Vulns
medium 4.3

CVE-2009-0781 json

Cross-site scripting in Apache Tomcat

published 2009-03-09 17 y ago modified 2026-06-16 4 mo ago also GHSA-j788-fx57-99wp , EUVD-2022-4299

cvss
4.3
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
9.7%
EPSS 9.7% chance of exploitation in 30 days, percentile 95%
public exploits
0
none known

Summary

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."

Patch / fix

  • maven org.apache.tomcat:tomcat 6.0.20
  • tomcat5 RHEL 2 APPLICATION_SERVER 5.5.23-0jpp_4rh.16
  • tomcat5-jasper RHEL 2 APPLICATION_SERVER 5.5.23-0jpp_4rh.16
  • tomcat5-webapps RHEL 2 APPLICATION_SERVER 5.5.23-0jpp_4rh.16
  • tomcat5-common-lib RHEL 2 APPLICATION_SERVER 5.5.23-0jpp_4rh.16
  • tomcat5-server-lib RHEL 2 APPLICATION_SERVER 5.5.23-0jpp_4rh.16
  • tomcat5-jsp-2.0-api RHEL 2 APPLICATION_SERVER 5.5.23-0jpp_4rh.16
  • tomcat5-admin-webapps RHEL 2 APPLICATION_SERVER 5.5.23-0jpp_4rh.16
  • tomcat5-jasper-javadoc RHEL 2 APPLICATION_SERVER 5.5.23-0jpp_4rh.16

red hat advisories RHSA-2009:1562RHSA-2009:1164

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2009-0781 updated cvss 4.3

tomcat: XSS in Apache Tomcat calendar application

  • Red Hat Application Server v2 4AS tomcat5 5.5.23-0jpp_4rh.16, tomcat5-jasper 5.5.23-0jpp_4rh.16, tomcat5-webapps 5.5.23-0jpp_4rh.16, tomcat5-common-lib 5.5.23-0jpp_4rh.16, tomcat5-server-lib 5.5.23-0jpp_4rh.16, tomcat5-jsp-2.0-api 5.5.23-0jpp_4rh.16, +5 more Red Hat Application Server v2 4ES tomcat5 5.5.23-0jpp_4rh.16, tomcat5-jasper 5.5.23-0jpp_4rh.16, tomcat5-webapps 5.5.23-0jpp_4rh.16, tomcat5-common-lib 5.5.23-0jpp_4rh.16, tomcat5-server-lib 5.5.23-0jpp_4rh.16, tomcat5-jsp-2.0-api 5.5.23-0jpp_4rh.16, +5 more Red Hat Application Server v2 4WS tomcat5 5.5.23-0jpp_4rh.16, tomcat5-jasper 5.5.23-0jpp_4rh.16, tomcat5-webapps 5.5.23-0jpp_4rh.16, tomcat5-common-lib 5.5.23-0jpp_4rh.16, tomcat5-server-lib 5.5.23-0jpp_4rh.16, tomcat5-jsp-2.0-api 5.5.23-0jpp_4rh.16, +5 more
    fixed: vendor fix RHSA-2009:1562
  • Red Hat Enterprise Linux (v. 5 server) tomcat5 5.5.23-0jpp.7.el5_3.2, tomcat5-jasper 5.5.23-0jpp.7.el5_3.2, tomcat5-webapps 5.5.23-0jpp.7.el5_3.2, tomcat5-common-lib 5.5.23-0jpp.7.el5_3.2, tomcat5-server-lib 5.5.23-0jpp.7.el5_3.2, tomcat5-jsp-2.0-api 5.5.23-0jpp.7.el5_3.2, +5 more Red Hat Enterprise Linux Desktop (v. 5 client) tomcat5 5.5.23-0jpp.7.el5_3.2, tomcat5-jasper 5.5.23-0jpp.7.el5_3.2, tomcat5-webapps 5.5.23-0jpp.7.el5_3.2, tomcat5-common-lib 5.5.23-0jpp.7.el5_3.2, tomcat5-server-lib 5.5.23-0jpp.7.el5_3.2, tomcat5-jsp-2.0-api 5.5.23-0jpp.7.el5_3.2, +5 more Red Hat Enterprise Linux Desktop Workstation (v. 5 client) tomcat5 5.5.23-0jpp.7.el5_3.2, tomcat5-jasper 5.5.23-0jpp.7.el5_3.2, tomcat5-webapps 5.5.23-0jpp.7.el5_3.2, tomcat5-common-lib 5.5.23-0jpp.7.el5_3.2, tomcat5-server-lib 5.5.23-0jpp.7.el5_3.2, tomcat5-jsp-2.0-api 5.5.23-0jpp.7.el5_3.2, +5 more
    fixed: vendor fix RHSA-2009:1164

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

9.72% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:P/A:N

Affected packages

ecosystem package affected fixed in
maven org.apache.tomcat:tomcat
>=4.1.0, <=4.1.39
>=5.5.0, <=5.5.27
>=6.0.0, <6.0.20
6.0.20

Classification

Weakness
  • CWE-79 Improper Neutralization of Input During Web Page Generation

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.