Quick answers
- Is CVE-2024-52318 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2024-52318 being exploited in the wild.
- How severe is CVE-2024-52318?
- Medium severity, with a CVSS score of 6.1, published 18 November 2024.
- Which products and versions are affected?
- Apache Tomcat 11.0.0, 10.1.31, 9.0.96; org.apache.tomcat:tomcat (Maven) ECOSYSTEM:introduced=11.0.0,fixed=11.0.1; org.apache.tomcat:tomcat-jasper (Maven) ECOSYSTEM:introduced=11.0.0,fixed=11.0.1; org.apache.tomcat.embed:tomcat-embed-jasper (Maven) ECOSYSTEM:introduced=9.0.96,fixed=9.0.97.
- Is there a fix for CVE-2024-52318?
- Yes. org.apache.tomcat:tomcat (Maven): upgrade to 11.0.1 or later; org.apache.tomcat:tomcat-jasper (Maven): upgrade to 11.0.1 or later; org.apache.tomcat.embed:tomcat-embed-jasper (Maven): upgrade to 9.0.97 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2024-52318 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2024-52318?
- Check whether you run Apache Tomcat, org.apache.tomcat:tomcat (Maven), org.apache.tomcat:tomcat-jasper (Maven) or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- org.apache.tomcat:tomcat (Maven): upgrade to 11.0.1 or later
# set org.apache.tomcat:tomcat to 11.0.1 in your pom.xml or build.gradle - org.apache.tomcat:tomcat-jasper (Maven): upgrade to 11.0.1 or later
# set org.apache.tomcat:tomcat-jasper to 11.0.1 in your pom.xml or build.gradle - org.apache.tomcat.embed:tomcat-embed-jasper (Maven): upgrade to 9.0.97 or later
# set org.apache.tomcat.embed:tomcat-embed-jasper to 9.0.97 in your pom.xml or build.gradle
Technical details
A regression introduced in a previous improvement caused pooled JSP tags not to be released after use. This failure in the tag lifecycle management results in subsequent tag outputs not being escaped as expected. An attacker can exploit this behavior to perform a Cross-Site Scripting (XSS) attack by injecting malicious content that the server fails to sanitize. The vulnerability affects Apache Tomcat versions 11.0.0, 10.1.31, and 9.0.96. Users should upgrade to versions 11.0.1, 10.1.33, or 9.0.97 to resolve the issue.
Affected products
- Apache Tomcat 11.0.0, 10.1.31, 9.0.96
Identifiers
- CVE-2024-52318
- GHSA-f632-9449-3j4w
Timeline
- 2024-11-18: disclosed
- 2024-11-18: advisory