CVE-2018-1275CWE-94

CVE-2018-1275: vulnerability in Spring Framework

Published · Updated

Follow this CVE+ Monitor Spring Framework+ Monitor org.springframework:spring-messaging

E-mail alert when it lands in KEV, gets a public PoC or its score goes up.

15Vexday Risk Score

No sign of exploitation. No public exploitation artifact known so far.

ssvc Trackepss 58%
What the vendors declare (VEX)

Official vendor statements in CSAF/VEX format: whether their product is affected, already fixed, or ruled out — and why. These are the vendor's assertions, not Vexday's judgment.

Red HatVEX document ↗
Affected
2 products
Red Hat JBoss Fuse 6 · Red Hat JBoss Fuse Integration Service 2
none_available: Affected
Fixed
2 products
Red Hat Fuse Intergration Services 2.0 based on Fuse 6.3 R8 · Red Hat Openshift Application Runtimes
fix ↗
Not affected
13 products (32 components) — because the vulnerable code is not present in the product
Red Hat Enterprise Linux 8 · Red Hat Fuse 7 · Red Hat JBoss A-MQ 6 · Red Hat JBoss BRMS 6 · Red Hat JBoss Data Virtualization 6 · and others 8
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.
Affected products
Spring by Pivotal · Spring Framework
Related CVEs — Spring Framework

In the same product, most dangerous first.

CVE-2018-1273CRITICALCVE-2018-1273EPSS 97.0%KEVCVE-2018-1270—CVE-2018-1270EPSS 77.6%CVE-2018-1271—CVE-2018-1271EPSS 30.3%CVE-2018-1272—CVE-2018-1272EPSS 3.1%CVE-2018-1274—CVE-2018-1274EPSS 1.9%