FreshPorts - VuXML

This page displays vulnerability information about FreeBSD Ports.

The VUXML data was last processed by FreshPorts on 2023-05-31 15:52:08 UTC

List all Vulnerabilities, by package

List all Vulnerabilities, by date

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

VuXML IDDescription
d34bef0b-f312-11eb-b12b-fc4dd43e2b6atomcat -- HTTP request smuggling in multiple versions

Bahruz Jabiyev, Steven Sprecher and Kaan Onarlioglu of NEU seclab reports:

Apache Tomcat did not correctly parse the HTTP transfer-encoding request header in some circumstances leading to the possibility to request smuggling when used with a reverse proxy. Specifically: Tomcat incorrectly ignored the transfer-encoding header if the client declared it would only accept an HTTP/1.0 response; Tomcat honoured the identify encoding; and Tomcat did not ensure that, if present, the chunked encoding was the final encoding.

Discovery 2021-05-07
Entry 2021-08-01
ge 8.5.0 le 8.5.66

ge 9.0.0 le 9.0.46

ge 10.0.0 le 10.0.6

cc7c85d9-f30a-11eb-b12b-fc4dd43e2b6atomcat -- Remote Denial of Service in multiple versions

rbeaudry reports:

A vulnerability in Apache Tomcat allows an attacker to remotely trigger a denial of service. An error introduced as part of a change to improve error handling during non-blocking I/O meant that the error flag associated with the Request object was not reset between requests. This meant that once a non-blocking I/O error occurred, all future requests handled by that request object would fail. Users were able to trigger non-blocking I/O errors, e.g. by dropping a connection, thereby creating the possibility of triggering a DoS.

Applications that do not use non-blocking I/O are not exposed to this vulnerability. This issue affects Apache Tomcat 10.0.3 to 10.0.4; 9.0.44; 8.5.64.

Discovery 2021-03-24
Entry 2021-08-01
eq 8.5.64

eq 9.0.44

ge 10.0.3 le 10.0.4

8b571fb2-f311-11eb-b12b-fc4dd43e2b6atomcat -- JNDI Realm Authentication Weakness in multiple versions

ilja.farber reports:

Queries made by the JNDI Realm did not always correctly escape parameters. Parameter values could be sourced from user provided data (eg user names) as well as configuration data provided by an administrator. In limited circumstances it was possible for users to authenticate using variations of their user name and/or to bypass some of the protection provided by the LockOut Realm.

Discovery 2021-04-08
Entry 2021-08-01
ge 7.0.0 le 7.0.108

ge 8.5.0 le 8.5.65

ge 9.0.0 le 9.0.45

ge 10.0.0 le 10.0.5