CVE-2018-1275 EPSS 57.4%

Spring Framework, versions 5.0 prior to 5.0.5 and versions 4.3 prior to 4.3.16 and older unsupported versions, allow…

Spring by Pivotal · Spring Framework

Summary

Spring Framework (versions before 5.0.5 in the 5.0 branch, before 4.3.16 in the 4.3 branch, and older unsupported versions) has a code injection flaw in the spring-messaging module's in-memory STOMP broker, which serves STOMP over WebSocket endpoints. An attacker who can send a crafted message to that broker can achieve remote code execution.

Official description · CVE.org

Spring Framework, versions 5.0 prior to 5.0.5 and versions 4.3 prior to 4.3.16 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. This CVE addresses the partial fix for CVE-2018-1270 in the 4.3.x branch of the Spring Framework.

Breakdown

20.5 / 100

Exploited: Not confirmed
Reports: 0
Tactics: 0/15

Disclosed on 11 Apr 2018. No public exploit code or confirmed exploitation is recorded.

See the family tree

A fix was bypassed or incomplete once over 5 weeks.

Same bug familyLinked by evidence that a fix failed or the same code was patched again. Oldest first.

CVE-2018-1270Spring Framework, versions 5.0 prior to 5.0.5 and versions 4.3…6 Apr 2018
incomplete fixHigh
Why these are linked:
- Stated in the CVE textThis CVE addresses the partial fix for CVE-2018-1270 in the 4.3.x branch of the Spring Framework.
- Similar weakness in the same product (machine-matched)same product + CWE + description similarity
This CVECVE-2018-1275Spring Framework, versions 5.0 prior to 5.0.5 and versions 4.3…11 Apr 2018
relatedMedium
Why these are linked:
- Same code patched: DefaultSubscriptionRegistry.java (machine-matched)Functions: DefaultSubscriptionRegistrycommit 246a6db commit ff2228f commit 0009806 commit e0de912
CVE-2018-1257Spring Framework, versions 5.0.x prior to 5.0.6, versions 4.3.x…11 May 2018

techniques

No techniques linked

No ATT&CK techniques are linked to this CVE yet. MITRE CTID has not mapped it, and no report passage in the corpus ties it to a technique.

Am I affected? What do I upgrade to?

From GitHub Security Advisories and OSV

1 package in 1 ecosystem. Main package: org.springframework:spring-messaging.

Mavenorg.springframework:spring-messagingGHSA-3rmv-2pg5-xvqj

Upgrade to 5.0.5.RELEASE or later

Fixes this CVE and 1 other known vulnerability in this package (CVE-2018-1270).

Set the version to 5.0.5.RELEASE or later in your pom.xml or build.gradle.

The first fix for CVE-2018-1275.

Affected versions, by release line

If you run	Upgrade to
5.0.0.RELEASE up to 5.0.5.RELEASE	5.0.5.RELEASE
All versions before 4.3.16.RELEASE	4.3.16.RELEASE

“Up to” means the second version is the fix and is not affected.

Check your lockfile against all CVEs

What security researchers reported

Not named in any threat report yet

Also mentioned in 1 community threat pulse (AlienVault OTX)

Weaker evidence

Pulses are indicator collections that anyone can publish. A mention is not confirmation of exploitation.

Thor Lite Scan - 10.7.15 - Ubuntu Scan on Archived Files21 May 2024

References

14 links, grouped by NVD tag

Exploitation evidence

Not in KEV. CISA has not confirmed exploitation.

ENISA

Not marked exploited. EUVD-2018-0490

No public exploit code found.

, 30 Oct 2026

57.4%Top 0.92%

Chance of exploitation in the next 30 days. of scored CVEs (riskier than 99.08%).

No CVSS score published.

Priority factorsFormula

In a KEV catalognot listed 0.0/35

Recent KEV listingnot listed 0.0/10

Known ransomware usenot known 0.0/10

EPSS percentilepercentile 0.9908 19.8/20

Threat reports0 reports 0.0/10

Public exploit codenone found 0.0/5

Mentioned in OTX pulses1 pulse 0.7/3

CVSS base scoreno CVSS 0.0/7

End-of-life productsupported or unknown 0.0

Total20.5

Record

Published: 11 Apr 2018
Modified: 17 Sep 2024
: CWE-94 Improper Control of Generation of Code
Elsewhere: NVD CVE.org JSON

Exploitation timelineExploitation timelineDated milestones for a CVE: when it was disclosed, when exploit code became public, when exploitation was confirmed, and when threat reports named it.

Patch historyPatch historyEarlier and later CVEs in the same code, in date order. It shows when a fix was bypassed or incomplete and which version finally fixed it.

Same bug familyLinked by evidence that a fix failed or the same code was patched again. Oldest first.

ATT&CKMITRE ATT&CKA public catalogue of the techniques attackers use, maintained by MITRE. Patchfirst uses it to describe what attackers do with a vulnerability. techniques

Am I affected? What do I upgrade to?

Affected versions, by release line

What security researchers reported

Also mentioned in 1 community threat pulse (AlienVault OTX)

References

vdb-entry 2

vendor-advisory 2

mailing-list 3

x_refsource_CONFIRM 4

x_refsource_MISC 3

techniques