Under some situations, the Spring Framework 4.2.0 to 4.2.1, 4.0.0 to 4.1.7, 3.2.0 to 3.2.14 and older unsupported versions is vulnerable to
Noroxi assessment
Priority: Monitor (action score 39/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 2.5% (FIRST EPSS); higher than 84.7% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- Fixed version: libspring-java (Debian:12) 4.1.9-1; libspring-java (Debian:8) 3.0.6.RELEASE-17+deb8u1; org.springframework:spring-core (Maven) 4.1.8, 4.2.2, 3.2.15.
Low priority for now. Upgrade to libspring-java (Debian:12) 4.1.9-1; libspring-java (Debian:8) 3.0.6.RELEASE-17+deb8u1; org.springframework:spring-core (Maven) 4.1.8, 4.2.2, 3.2.15 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Under some situations, the Spring Framework 4.2.0 to 4.2.1, 4.0.0 to 4.1.7, 3.2.0 to 3.2.14 and older unsupported versions is vulnerable to a Reflected File Download (RFD) attack. The attack involves a malicious user crafting a URL with a batch script extension that results in the response being downloaded rather than rendered and also includes some input reflected in the response.
- Published
- May 25, 2017
- Updated
- Jun 16, 2026
- EPSS
- 2.5% · 84th percentile
- CWE
- CWE-552
Report tools
Action score
39
Monitor
Low priority for now.
- CVSS
- 38 / 40 · 9.6 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.5%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| vmware | spring framework | cpe:2.3:a:vmware:spring_framework |
| debian | debian linux | cpe:2.3:o:debian:debian_linux |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux8.0
- vmware spring framework3.2.0
- vmware spring framework3.2.1
- vmware spring framework3.2.10
- vmware spring framework3.2.11
- vmware spring framework3.2.12
- vmware spring framework3.2.13
- vmware spring framework3.2.14
- vmware spring framework3.2.2
- vmware spring framework3.2.3
- vmware spring framework3.2.4
- vmware spring framework3.2.5
- vmware spring framework3.2.6
- vmware spring framework3.2.7
- vmware spring framework3.2.8
- vmware spring framework3.2.9
- vmware spring framework4.0.0
- vmware spring framework4.0.1
- vmware spring framework4.0.2
- vmware spring framework4.0.3
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | libspring-java | before 4.1.9-1 | 4.1.9-1 |
| Debian:8 | libspring-java | before 3.0.6.RELEASE-17+deb8u1 | 3.0.6.RELEASE-17+deb8u1 |
| Maven | org.springframework:spring-core | from 4.0.0 · before 4.1.8 | 4.1.8 |
| Maven | org.springframework:spring-core | from 4.2.0 · before 4.2.2 | 4.2.2 |
| Maven | org.springframework:spring-core | before 3.2.15 | 3.2.15 |
Same product
vmware: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-22965A Spring MVC or Spring WebFlux application running on JDK 9+ may be vulnerable to remote code execution (RCE) via data binding.KEV99Now
- CVE-2018-1270Spring 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 62This week
- CVE-2020-5398RFD Attack via "Content-Disposition" Header Sourced from Request Input by Spring MVC or Spring WebFlux Application57Plan
- CVE-2018-1275Spring 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 56Plan
- CVE-2016-1000027Pivotal Spring Framework through 5.3.16 suffers from a potential remote code execution (RCE) issue if used for Java deserialization of untru49Plan
- CVE-2026-59313Server Sent Event stream corruption in Spring MVC functional web framework39Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:libspring-java | 4.1.9-1 · Debian:12 | Package registry (OSV) |
| Maven:org.springframework:spring-core | 3.2.15 | Package registry (OSV) |
| Maven:org.springframework:spring-core | 4.1.8 | Package registry (OSV) |
| Maven:org.springframework:spring-core | 4.2.2 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-552 · Files or Directories Accessible to External PartiesCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
- OS Credential DumpingT1003
- Data from Network Shared DriveT1039
- Automated CollectionT1119
- Data from Information RepositoriesT1213
- Data from Cloud Storage ObjectT1530
- Unsecured Credentials: Credentials in FilesT1552.001
- Unsecured Credentials: Bash HistoryT1552.003
- Unsecured Credentials: Private KeysT1552.004
- Unsecured Credentials: Group Policy PreferencesT1552.006
- Credentials from Password StoresT1555
- Data from Configuration RepositoryT1602
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.