CVE-2018-15756
No source can show you its own past. This one can.
Print this page to keep the view as it stands on this date. Everything hidden behind a disclosure opens, and every receipt prints with its value.
DoS Attack via Range Requests
rank 38 = 2 + 19 + 1 + 16 + 0
rank@v1 · scheduled
Someone is already using it
CISA KEV catalog · public proof-of-concept · FIRST EPSS
EPSS 0.09207 · without this subject the record ranks 36
What it costs you if it fires
NVD CVSS base score, then the CNA's own
CVSS 7.5, from NVD · without this subject the record ranks 19
It is getting worse, not staying still
FIRST EPSS series, rescorings and bad loads removed
rose on 2025-12-08 · without this subject the record ranks 37
How much of the world it touches
NVD CPE configurations
114 products in the CPE ranges · without this subject the record ranks 22
Someone else already set the date
CISA KEV remediation due date
no CISA due date · without this subject the record ranks 38
Hindsight · the state
Foresight · where to check next
No weakness class or product neighbourhood is held for this record, so this index cannot name anywhere to check next. That is an absence in the record, not a finding about the software.
Sources disagree here.
Both shown, dated. We don't pick winners. disagreement-rules@v1
Running Pivotal Spring framework? Check your version
A deterministic range check against the ranges this record publishes. It tells you where a version sits in the record, not whether your deployment is exploitable. No account needed.
Watch this record
Matches your own product list against every record this index holds, and tells you when one of them moves.
Watch Pivotal Spring framework
Set up a watchlist (free with an account: one stack of three products)
Record your call
Keep your verdict, your reason and the evidence together. The record takes its date when you save it.
Or open an investigation: an incident or a near miss on this CVE, kept with its evidence where anyone in your organisation can find it.
Choose your verdict, then sign in or use an email link. Your first 100 records are free. Evidence is frozen when the record is created.
Private to your organization unless you share it. Put the proof link in your ticket so a reviewer can inspect the basis for your call. See how decision records work.
Harm, if it fires from the vector and the weakness
Written for the ticket you're about to file.
CISA KEV & Federal Remediation Deadline from the record and CISA
The fix, and how long it's been waiting.
Show full BOD 26-04 deadline
CISA has not scored it, so the directive's own defaults apply: automatable no, technical impact total. Calendar days from the KEV listing or from when you find it on a system, whichever is first. Federal agencies are bound from 7 Dec 2026, and contracts often carry it to suppliers. The directive and its table
Exploit Status & Known PoCs a ladder, not a score
Current rung: Nothing observed in held sources.
- RUNG 1Nothing observed in held sources
- RUNG 2Proof-of-concept published
- RUNG 3Exploited in the wild · CISA KEV listed
- RUNG 4Ransomware campaign use known
Affected & Fixed Versions as published
Show all 114 published ranges
A rung lights from a row in the index, never from an assessment. "Held sources" is the true scope of the claim: this index reads the CVE record, NVD, CISA KEV, FIRST's EPSS and public proof-of-concept repositories, and it does not observe attacks.
$281,000 = $4.99M incident cost x 0.6121449559255632 exposure x 0.09207 likelihood
udv@v1 · unaudited · wrong for you until you say what you run
$4.99M is the cost of a breach that happened, from IBM Cost of a Data Breach Report 2026, global average. It is not the value of any asset of yours. That average already covers breaches of every severity, so scaling it by exposure understates a partial-impact record. That is an assumption, not a measurement. Your own asset value goes in the decision record.
What it is stated by the CNA
Spring Framework, version 5.1, versions 5.0.x prior to 5.0.10, versions 4.3.x prior to 4.3.20, and older unsupported versions on the 4.2.x branch provide support for range requests when serving static resources through the ResourceHttpRequestHandler, or starting in 5.0 when an annotated controller returns an org.springframework.core.io.Resource. A malicious user (or attacker) can add a range header with a high number of ranges, or with wide ranges that overlap, or both, for a denial of service attack. This vulnerability affects applications that depend on either spring-webmvc or spring-webflux. Such applications must also have a registration for serving static resources (e.g. receipt
Read the rest of the CNA's description
JS, CSS, images, and others), or have an annotated controller that returns an org.springframework.core.io.Resource. Spring Boot applications that depend on spring-boot-starter-web or spring-boot-starter-webflux are ready to serve static resources out of the box and are therefore vulnerable.
NVD's analysis a second authority
- severity
- 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- affected versions
- vmware spring framework >= 4.2.0 < 4.3.20; vmware spring framework >= 5.0.0 < 5.0.10; vmware spring framework 5.1.0; and 111 more, listed in full below
check it yourself securityfocus.com lists.apache.org lists.apache.org lists.apache.org lists.apache.org lists.apache.org +14 morereceipt
Dated events
Movement the material steps
This score more than doubled inside 72 hours. Both observations are in the full history below.
Show all 54 observations
54 observations held. A highlighted step crossed a promotion threshold. A step marked with a scoring model moved because the instrument was replaced, not because the vulnerability changed. receipt
The full biography
Exploit probability more than doubled between 2025-05-01 and 2025-05-04 (0.03621 → 0.09613) and the record had been public for 7 years, 10 months when this index was last written.
Siblings and hubs
Records related to this one
None. No alias set, and nothing in the corpus cites this identifier or shares its product family within 60 days.
Browse the index from here
These are index-wide views, not findings about CVE-2018-15756.
What usually comes next
Everything above needs no account. What is below is work: assembling it, scoping it to your estate, watching it, and handing it to someone else.