VYPR

Undertow

by Red Hat

Source repositories

CVEs (42)

  • CVE-2022-4492HigFeb 23, 2023
    risk 0.42cvss 7.5epss 0.01

    The undertow client is not checking the server identity presented by the server certificate in https connections. This is a compulsory step (at least it should be performed by default) in https and in http/2. I would add it to any TLS client protocol.

  • CVE-2021-3859HigAug 26, 2022
    risk 0.42cvss 7.5epss 0.01

    A flaw was found in Undertow that tripped the client-side invocation timeout with certain calls made over HTTP2. This flaw allows an attacker to carry out denial of service attacks.

  • CVE-2021-3690HigAug 23, 2022
    risk 0.42cvss 7.5epss 0.01

    A flaw was found in Undertow. A buffer leak on the incoming WebSocket PONG message may lead to memory exhaustion. This flaw allows an attacker to cause a denial of service. The highest threat from this vulnerability is availability.

  • CVE-2020-10719MedMay 26, 2020
    risk 0.42cvss 6.5epss 0.01

    A flaw was found in Undertow in versions before 2.1.1.Final, regarding the processing of invalid HTTP requests with large chunk sizes. This flaw allows an attacker to take advantage of HTTP request smuggling.

  • CVE-2019-10184HigJul 25, 2019
    risk 0.42cvss 7.5epss 0.03

    undertow before version 2.0.23.Final is vulnerable to an information leak issue. Web apps may have their directory structures predicted through requests without trailing slashes via the api.

  • CVE-2018-1114MedSep 11, 2018
    risk 0.42cvss 6.5epss 0.02

    It was found that URLResource.getLastModified() in Undertow closes the file descriptors only when they are finalized which can cause file descriptors to exhaust. This leads to a file handler leak.

  • CVE-2017-2666MedJul 27, 2018
    risk 0.42cvss 6.5epss 0.03

    It was discovered in Undertow that the code that parsed the HTTP request line permitted invalid characters. This could be exploited, in conjunction with a proxy that also permitted the invalid characters but with a different interpretation, to inject data into the HTTP response.…

  • CVE-2018-1067MedMay 21, 2018
    risk 0.40cvss 6.1epss 0.02

    In Undertow before versions 7.1.2.CR1, 7.1.2.GA it was found that the fix for CVE-2016-4993 was incomplete and Undertow web server is vulnerable to the injection of arbitrary HTTP headers, and also response splitting, due to insufficient sanitization and validation of user input…

  • CVE-2017-7559MedJan 10, 2018
    risk 0.40cvss 6.1epss 0.02

    In Undertow 2.x before 2.0.0.Alpha2, 1.4.x before 1.4.17.Final, and 1.3.x before 1.3.31.Final, it was found that the fix for CVE-2017-2666 was incomplete and invalid characters are still allowed in the query string and path parameters. This could be exploited, in conjunction…

  • CVE-2021-3629MedMay 24, 2022
    risk 0.38cvss 5.9epss 0.01

    A flaw was found in Undertow. A potential security issue in flow control handling by the browser over http/2 may potentially cause overhead or a denial of service in the server. The highest threat from this vulnerability is availability. This flaw affects Undertow versions prior…

  • CVE-2021-3597MedMay 24, 2022
    risk 0.38cvss 5.9epss 0.01

    A flaw was found in undertow. The HTTP2SourceChannel fails to write the final frame under some circumstances, resulting in a denial of service. The highest threat from this vulnerability is availability. This flaw affects Undertow versions prior to 2.0.35.SP1, prior to…

  • CVE-2018-14642MedSep 18, 2018
    risk 0.35cvss 5.3epss 0.02

    An information leak vulnerability was found in Undertow. If all headers are not written out in the first write() call then the code that handles flushing the buffer will always write out the full contents of the writevBuffer buffer, which may contain data from previous requests.

  • CVE-2022-2764MedSep 1, 2022
    risk 0.32cvss 4.9epss 0.01

    A flaw was found in Undertow. Denial of service can be achieved as Undertow server waits for the LAST_CHUNK forever for EJB invocations.

  • CVE-2020-10687MedSep 23, 2020
    risk 0.31cvss 4.8epss 0.01

    A flaw was discovered in all versions of Undertow before Undertow 2.2.0.Final, where HTTP request smuggling related to CVE-2017-2666 is possible against HTTP/1.x and HTTP/2 due to permitting invalid characters in an HTTP request. This flaw allows an attacker to poison a…

  • CVE-2024-1459MedFeb 12, 2024
    risk 0.28cvss 5.3epss 0.02

    A path traversal vulnerability was found in Undertow. This issue may allow a remote attacker to append a specially-crafted sequence to an HTTP request for an application deployed to JBoss EAP, which may permit access to privileged or restricted files and directories.

  • CVE-2021-20220MedFeb 23, 2021
    risk 0.24cvss 4.8epss 0.01

    A flaw was found in Undertow. A regression in the fix for CVE-2020-10687 was found. HTTP request smuggling related to CVE-2017-2666 is possible against HTTP/1.x and HTTP/2 due to permitting invalid characters in an HTTP request. This flaw allows an attacker to poison a…

  • CVE-2017-12196MedApr 18, 2018
    risk 0.24cvss 4.8epss 0.02

    undertow before versions 1.4.18.SP1, 2.0.2.Final, 1.4.24.Final was found vulnerable when using Digest authentication, the server does not ensure that the value of URI in the Authorization header matches the URI in HTTP request line. This allows the attacker to cause a MITM…

  • CVE-2017-12165LowJul 27, 2018
    risk 0.10cvss 2.6epss 0.02

    It was discovered that Undertow before 1.4.17, 1.3.31 and 2.0.0 processes http request headers with unusual whitespaces which can cause possible http request smuggling.

  • CVE-2014-7816Dec 1, 2014
    risk 0.05cvss epss 0.25

    Directory traversal vulnerability in JBoss Undertow 1.0.x before 1.0.17, 1.1.x before 1.1.0.CR5, and 1.2.x before 1.2.0.Beta3, when running on Windows, allows remote attackers to read arbitrary files via a .. (dot dot) in a resource URI.

  • CVE-2022-1319HigAug 31, 2022
    risk 0.00cvss 7.5epss 0.01

    A flaw was found in Undertow. For an AJP 400 response, EAP 7 is improperly sending two response packets, and those packets have the reuse flag set even though JBoss EAP closes the connection. A failure occurs when the connection is reused after a 400 by CPING since it reads in…