AsyncHttpClient: WebSocket handshake continues after a failed Sec-WebSocket-Accept check
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| AsyncHttpClient | async-http-client | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Asynchttpclient Project | Async-http-client |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.138% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Asynchttpclient Project
Asynchttpclient Project async-http-client |
|
| Vendors & Products |
Asynchttpclient Project
Asynchttpclient Project async-http-client |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | The AsyncHttpClient (AHC) library allows Java applications to easily execute HTTP requests and asynchronously process HTTP responses. Prior to 3.0.12 and 2.16.1, WebSocketHandler.upgrade aborts a handshake whose Sec-WebSocket-Accept value is missing or invalid but continues into pipeline installation and onOpen delivery. Frames coalesced with the invalid 101 response can be decoded and delivered from a peer that did not prove the handshake, although the request future fails and the channel closes. This issue is fixed in versions 3.0.12 and 2.16.1. | |
| Title | AsyncHttpClient: WebSocket handshake continues after a failed Sec-WebSocket-Accept check | |
| Weaknesses | CWE-345 CWE-670 |
|
| References |
|
|
| Metrics |
cvssV3_1
|