2 results (0.027 seconds)

CVSS: 7.5EPSS: 0%CPEs: 4EXPL: 0

Versions of Async HTTP Client prior to 1.13.2 are vulnerable to a form of targeted request manipulation called CRLF injection. This vulnerability was the result of insufficient validation of HTTP header field values before sending them to the network. Users are vulnerable if they pass untrusted data into HTTP header field values without prior sanitisation. Common use-cases here might be to place usernames from a database into HTTP header fields. This vulnerability allows attackers to inject new HTTP header fields, or entirely new requests, into the data stream. • https://github.com/swift-server/async-http-client/security/advisories/GHSA-v3r5-pjpm-mwgq • CWE-74: Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') CWE-93: Improper Neutralization of CRLF Sequences ('CRLF Injection') •

CVSS: 7.5EPSS: 0%CPEs: 1EXPL: 0

Async Http Client (aka async-http-client) before 2.0.35 can be tricked into connecting to a host different from the one extracted by java.net.URI if a '?' character occurs in a fragment identifier. Similar bugs were previously identified in cURL (CVE-2016-8624) and Oracle Java 8 java.net.URL. Async Http Client (también async-http-client) en versiones anteriores a la 2.0.35 se puede engañar para que se conecte a otro host diferente del extraído por java.net.URI si existe el caracter '?' en un identificador de fragmento. • http://openwall.com/lists/oss-security/2017/08/31/4 https://access.redhat.com/errata/RHSA-2018:2669 https://github.com/AsyncHttpClient/async-http-client/issues/1455 https://lists.apache.org/thread.html/r04b15fd898a6b1612153543375daaa8145a0fd1804ec9fa2e0d95c97%40%3Cissues.tez.apache.org%3E https://lists.apache.org/thread.html/r0a6b6429a7558051dbb70bd06584b4b1c334a80ec9203d3d39b7045a%40%3Ccommits.tez.apache.org%3E https://lists.apache.org/thread.html/r14a74d204f285dd3a4fa203de6dbb4e741ddb7fdfff7915590e5b3db%40%3Cdev.tez.apache.org%3E https:/ • CWE-20: Improper Input Validation •