CVE-2019-17598: Play Framework Inadequate Encryption Strength vulnerability
7.5
CVSS Score
3.1
Basic Information
CVE ID
GHSA ID
EPSS Score
0.36203%
CWE
Published
5/24/2022
Updated
2/2/2023
KEV Status
No
Technology
Java
Technical Details
CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
| Package Name | Ecosystem | Vulnerable Versions | First Patched Version |
|---|---|---|---|
| com.typesafe.play:play-ws_2.12 | maven | >= 2.5.0, < 2.6.24 | 2.6.24 |
Vulnerability Intelligence
Miggo AI
Root Cause Analysis
The vulnerability stems from Play-WS improperly including proxy credentials in HTTP CONNECT requests during HTTPS tunneling. Key functions identified are:
- ProxyServer.addAuthorizationHeader: Directly handles proxy auth headers in AsyncHttpClient (used by Play-WS).
- AhcWSClientConfig.buildProxyServer: Configures proxy credentials at the Play-WS/AHC integration layer.
- ChannelManager.createConnection: Manages connection reuse where credential leakage could occur under high load. These functions align with the described vulnerability mechanism (credentials in CONNECT requests) and Play Framework's architecture using AsyncHttpClient.