FreshPorts - VuXML

This page displays vulnerability information about FreeBSD Ports.

The VUXML data was last processed by FreshPorts on 2025-07-21 20:49:39 UTC

List all Vulnerabilities, by package

List all Vulnerabilities, by date

k68

These are the vulnerabilities relating to the commit you have selected:

VuXML IDDescription
ed0a052a-c5e6-11ef-a457-b42e991fc52eApache Tomcat -- RCE due to TOCTOU issue in JSP compilation

security@apache.org reports:

Time-of-check Time-of-use (TOCTOU) Race Condition The mitigation for CVE-2024-50379 was incomplete. Users running Tomcat on a case insensitive file system with the default servlet write enabled (readonly initialisation parameter set to the non-default value of false) may need additional configuration to fully mitigate CVE-2024-50379 depending on which version of Java they are using with Tomcat: - running on Java 8 or Java 11: the system propertysun.io.useCanonCaches must be explicitly set to false (it defaults to true) - running on Java 17: thesystem property sun.io.useCanonCaches, if set, must be set to false(it defaults to false) - running on Java 21 onwards: no further configuration is required(the system property and the problematic cache have been removed) Tomcat 11.0.3, 10.1.35 and 9.0.99 onwards will include checks thatsun.io.useCanonCaches is set appropriately before allowing the default servlet to be write enabled on a case insensitive file system. Tomcat will also setsun.io.useCanonCaches to false by default where it can.


Discovery 2024-12-20
Entry 2024-12-29
tomcat110
> 11.0.0 lt 11.0.1

tomcat101
> 10.1.0 lt 10.1.33

tomcat9
> 9.0.0 lt 9.0.97

CVE-2024-56337
https://nvd.nist.gov/vuln/detail/CVE-2024-56337
ef87346f-5dd0-11f0-beb2-ac5afc632ba3Apache Tomcat -- Multiple Vulnerabilities

security@apache.org reports:

A race condition on connection close could trigger a JVM crash when using the APR/Native connector leading to a DoS. This was particularly noticeable with client initiated closes of HTTP/2 connections.

An uncontrolled resource consumption vulnerability if an HTTP/2 client did not acknowledge the initial settings frame that reduces the maximum permitted concurrent streams could result in a DoS.

For some unlikely configurations of multipart upload, an Integer Overflow vulnerability could lead to a DoS via bypassing of size limits.


Discovery 2025-07-10
Entry 2025-07-10
Modified 2025-07-15
tomcat110
>= 11.0.0 lt 11.0.9

tomcat101
>= 10.1.0 lt 10.1.43

tomcat9
>= 9.0.0 lt 9.0.107

CVE-2025-52434
https://nvd.nist.gov/vuln/detail/CVE-2025-52434
CVE-2025-52520
https://nvd.nist.gov/vuln/detail/CVE-2025-52520
CVE-2025-53506
https://nvd.nist.gov/vuln/detail/CVE-2025-53506