Play Framework Inadequate Encryption Strength vulnerability

published 2019-11-05 7y ago modified 2026-06-17 4mo ago also GHSA-442g-gcg6-mhm4 , EUVD-2022-2289

cvss: 7.5; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.7%; EPSS 0.7% chance of exploitation in 30 days, percentile 53%
public exploits: 0; none known

An issue was discovered in Lightbend Play Framework 2.5.x through 2.6.23. When configured to make requests using an authenticated HTTP proxy, play-ws may sometimes, typically under high load, when connecting to a target host using https, expose the proxy credentials to the target host.

Patch / fix

fixed in 1

maven com.typesafe.play:play-ws_2.12 2.6.24

Is CVE-2019-17598 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.70% chance of exploitation in the next 30 days, higher than 53% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.1	7.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NVD	2.0	4.3	AV:N/AC:M/Au:N/C:P/I:N/A:N
GitHub	3.1	7.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem	package	affected	fixed in
maven	com.typesafe.play:play-ws_2.12	>=2.5.0, <2.6.24	2.6.24

Classification

Weakness

CWE-326 Inadequate Encryption Strength

References

playframework.com /security/vulnerability
web, release-notes, vendor-advisory
playframework.com /security/vulnerability/CVE-2019-17598-PlayWSHttpConnectAuthorizationHeaders
web, vendor-advisory
nvd.nist.gov /vuln/detail/CVE-2019-17598
advisory

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.