# CVE-2019-17598: Play Framework Inadequate Encryption Strength vulnerability

> Authenticated proxy credentials may be exposed to target hosts when using HTTPS under high load in the Play Framework HTTP client library.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Nov 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-442g-gcg6-mhm4

## What is CVE-2019-17598?

CVE-2019-17598 is a high-severity vulnerability in n/a, published on 5 Nov 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-326 (Inadequate Encryption Strength)

## Which versions are affected by CVE-2019-17598?

2 open source packages ship an affected version, including com.typesafe.play:play-ws_2.12. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.typesafe.play:play-ws_2.12` | Maven | From 2.5.0 | 2.6.24 |
| `com.typesafe.play:play-ws_2.12` | Maven | From 2.5.0 | 2.6.24 |

Products: Lightbend Play Framework.

## How do I fix CVE-2019-17598?

Upgrade com.typesafe.play:play-ws_2.12 to 2.6.24 or later.

## Is CVE-2019-17598 being exploited?

There is no known exploitation of CVE-2019-17598 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2014-3630](https://insights.sbomify.com/CVE-2014-3630/): XML external entity in n/a (critical 9.8)
- [CVE-2022-31018](https://insights.sbomify.com/CVE-2022-31018/): Denial of service binding form from JSON in Play Framework (high 7.5)
- [CVE-2020-26882](https://insights.sbomify.com/CVE-2020-26882/): Data Amplification in Play Framework (high 7.5)
- [CVE-2020-26883](https://insights.sbomify.com/CVE-2020-26883/): Uncontrolled Recursion in Play Framework (high 7.5)
- [CVE-2020-27196](https://insights.sbomify.com/CVE-2020-27196/): Out-of-bounds Write in Play Framework (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-17598 and fix it if it is affected.

What it is: CVE-2019-17598 is a high-severity vulnerability in n/a, published on 5 Nov 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-17598 in the wild and no public exploit code.

Affected packages and fixed versions:
- com.typesafe.play:play-ws_2.12 (Maven): affected from 2.5.0; fixed in 2.6.24
- com.typesafe.play:play-ws_2.12 (Maven): affected from 2.5.0; fixed in 2.6.24

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-17598/ (Markdown: https://insights.sbomify.com/CVE-2019-17598/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-17598
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-17598
- OSV: https://osv.dev/vulnerability/CVE-2019-17598

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-17598/
Summaries are generated and may contain mistakes; the official description above is the record.