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

GHSA-q8xj-8xg3-w432

HIGH

GHSA-q8xj-8xg3-w432 is a high-severity (CVSS 7.5) Uncontrolled Resource Consumption vulnerability in io.spray:spray-json_2.12. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether GHSA-q8xj-8xg3-w432 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Uncontrolled Resource Consumption in spray-json

Also known asCVE-2018-18854
Published
Nov 9, 2018
Updated
Nov 8, 2023
Affected
3 pkgs
Patched
3 / 3
Exploits
1 known
Exploitation data as of Nov 8, 2023 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

3 pkgs affected
io.spray:spray-json_2.12io.spray:spray-json_2.11io.spray:spray-json_2.10

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

Lightbend Spray spray-json through 1.3.4 allows remote attackers to cause a denial of service (resource consumption) because of Algorithmic Complexity during the parsing of many JSON object fields (with keys that have the same hash code).

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
Mavenio.spray:spray-json_2.12all versions1.3.5
Mavenio.spray:spray-json_2.11all versions1.3.5
Mavenio.spray:spray-json_2.10all versions1.3.5
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for io.spray:spray-json_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 io.spray:spray-json_2.12 to 1.3.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-q8xj-8xg3-w432 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-q8xj-8xg3-w432 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-q8xj-8xg3-w432. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Lightbend Spray spray-json through 1.3.4 allows remote attackers to cause a denial of service (resource consumption) because of Algorithmic Complexity during the parsing of many JSON object fields (with keys that have the same hash code).
O3 Security · Impact-Aware SCA

Is GHSA-q8xj-8xg3-w432 in your dependencies?

O3 detects GHSA-q8xj-8xg3-w432 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.