Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven

GHSA-rqph-vqwm-22vc

MEDIUM

GHSA-rqph-vqwm-22vc is a medium-severity (CVSS 6.5) CWE-770 vulnerability in org.springframework:spring-messaging. O3 Security confirms whether GHSA-rqph-vqwm-22vc is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Allocation of Resources Without Limits or Throttling in Spring Framework

Also known asCVE-2022-22971
Published
May 13, 2022
Updated
Mar 14, 2024
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed

Blast Radius

2 pkgs affected
org.springframework:spring-messagingorg.springframework:spring-messaging

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

In spring framework versions prior to 5.3.20+ , 5.2.22+ and old unsupported versions, application with a STOMP over WebSocket endpoint is vulnerable to a denial of service attack by an authenticated user.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
Mavenorg.springframework:spring-messaging5.3.0&&< 5.3.205.3.20
Mavenorg.springframework:spring-messagingall versions5.2.22.RELEASE

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework:spring-messaging. 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 org.springframework:spring-messaging to 5.3.20 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rqph-vqwm-22vc 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-rqph-vqwm-22vc 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-rqph-vqwm-22vc. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

In spring framework versions prior to 5.3.20+ , 5.2.22+ and old unsupported versions, application with a STOMP over WebSocket endpoint is vulnerable to a denial of service attack by an authenticated user.
O3 Security · Impact-Aware SCA

Is GHSA-rqph-vqwm-22vc in your dependencies?

O3 detects GHSA-rqph-vqwm-22vc across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.