Allocation of Resources Without Limits or Throttling in Spring FrameworkGHSA-rqph-vqwm-22vc
MEDIUMFix: spring-projects/spring-framework@159a99bGHSA-rqph-vqwm-22vc is a medium-severity (CVSS 6.5) CWE-770 vulnerability in org.springframework:spring-messaging. A fix is available for org.springframework:spring-messaging — see the affected versions and patch details below.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.springframework:spring-messaging☕org.springframework:spring-messagingReal-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
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.springframework:spring-messaging | ≥ 5.3.0&&< 5.3.20 | 5.3.20org.springframework:spring-messaging:5.3.20 |
| ☕Maven | org.springframework:spring-messaging | all versions | 5.2.22.RELEASEorg.springframework:spring-messaging:5.2.22.RELEASE |
Affected Products
cloud secure agentnetapponcommand insightnetappfinancial services crime and compliance management studiooraclespring frameworkvmwareDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework:spring-messaging, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
| Product | Fixed in | Advisory |
|---|---|---|
| AMQ Broker 7.10.3 | springframework | RHSA-2023:3185 |
| AMQ Broker 7.11.0 | see advisory | RHSA-2023:1661 |
| Red Hat Fuse 7.11 | springframework | RHSA-2022:5532 |
Frequently Asked Questions
Is GHSA-rqph-vqwm-22vc in your dependencies?
Find it across Maven, including transitive dependencies.