Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven
Not in CISA KEV
HIGH severity

GHSA-442g-gcg6-mhm4

HIGH

GHSA-442g-gcg6-mhm4 is a high-severity (CVSS 7.5) CWE-326 vulnerability in com.typesafe.play:play-ws_2.12. O3 Security confirms whether GHSA-442g-gcg6-mhm4 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Play Framework Inadequate Encryption Strength vulnerability

Also known asCVE-2019-17598
Published
May 24, 2022
Updated
Nov 8, 2023
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 8, 2023 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
com.typesafe.play:play-ws_2.12

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
Mavencom.typesafe.play:play-ws_2.122.5.0&&< 2.6.242.6.24

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.typesafe.play:play-ws_2.12. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update com.typesafe.play:play-ws_2.12 to 2.6.24 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-442g-gcg6-mhm4 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-442g-gcg6-mhm4 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-442g-gcg6-mhm4. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is GHSA-442g-gcg6-mhm4 in your dependencies?

O3 detects GHSA-442g-gcg6-mhm4 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

GHSA-442g-gcg6-mhm4: play-ws_2.12 (High… | O3 Security