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

CVE-2018-1270

CRITICAL

CVE-2018-1270 is a critical-severity (CVSS 9.8) Code Injection vulnerability in org.springframework:spring-messaging. 6 public exploit references exist, so weaponization risk is real. O3 Security confirms whether CVE-2018-1270 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Spring Framework allows applications to expose STOMP over WebSocket endpoints

Also known asGHSA-p5hg-3xm3-gcjg
Published
Apr 6, 2018
Updated
Jul 8, 2026
Affected
2 pkgs
Patched
2 / 2
Exploits
6 known

Blast Radius

2 pkgs affected
☕org.springframework:spring-messaging☕org.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

Spring Framework, versions 5.0 prior to 5.0.5 and versions 4.3 prior to 4.3.15 and older unsupported versions, allow applications to expose STOMP over WebSocket endpoints with a simple, in-memory STOMP broker through the spring-messaging module. A malicious user (or attacker) can craft a message to the broker that can lead to a remote code execution attack.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenorg.springframework:spring-messaging≥ 5.0.0.RELEASE&&< 5.0.5.RELEASE5.0.5.RELEASE
☕Mavenorg.springframework:spring-messagingall versions4.3.16.RELEASE
Exploits & PoCs
6

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 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.0.5.RELEASE or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-1270 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 CVE-2018-1270 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 CVE-2018-1270. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Spring Framework, versions 5.0 prior to 5.0.5 and versions 4.3 prior to 4.3.15 and older unsupported versions, allow applications to expose STOMP over WebSocket endpoints with a simple, in-memory STOMP broker through the spring-messaging module. A malicious user (or attacker) can craft a message to the broker that can lead to a remote code execution attack.
O3 Security · Impact-Aware SCA

Is CVE-2018-1270 in your dependencies?

O3 detects CVE-2018-1270 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works