Async Http Client
Approved changes feed: RSS · Atom
cpe:2.3:a:asynchttpclient_project:async-http-client:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Asynchttpclient Project (e8247b1b-f0e7-5b6c-b4ab-bbf4834de5cc) |
|---|---|
| Product | Async Http Client (8257a1b6-ab6c-5b2b-b4c2-d1a99973348e) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from purl2cpe mapping |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:deb/debian/async-http-client |
purl2cpe | 2026-06-01 10:17:01.453649 |
pkg:github/asynchttpclient/async-http-client |
purl2cpe | 2026-06-01 10:17:01.453651 |
pkg:maven/org.asynchttpclient/async-http-client-project |
purl2cpe | 2026-06-01 10:17:01.453653 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2024-53990 |
vulnerable | 2026-06-08 06:54:15.812503 |
AsyncHttpClient (AHC) library's `CookieStore` replaces explicitly defined `Cookie`s
The AsyncHttpClient (AHC) library allows Java applications to easily execute HTTP requests and asynchronously process HTTP responses. When making any HTTP request, the automatically enabled and self-managed CookieStore (aka cookie jar) will silently replace explicitly defined Cookies with any that have the same name from the cookie jar. For services that operate with multiple users, this can result in one user's Cookie being used for another user's requests.
Published: 2024-12-02T17:10:28.229Z
Updated: 2024-12-04T17:08:11.472Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-0040 |
vulnerable | 2026-06-08 05:52:04.130643 |
Details available
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. This can cause requests to be understood very differently by the remote server than was intended. In general, this is unlikely to result in data disclosure, but it can result in a number of logical errors and other misbehaviours.
Published: 2023-01-18T00:00:00.000Z
Updated: 2025-04-03T19:28:55.800Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2017-14063 |
vulnerable | 2026-06-08 05:08:49.168432 |
Details available
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.
Published: 2017-08-31T16:00:00.000Z
Updated: 2024-08-05T19:13:41.830Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.