cve.bz

CVE-2017-8046 Improper Input Validation

9.8 criticalExploitEPSS 75%Fix available

Critical (9.8). EPSS 75% estimated probability of exploitation activity in the next 30 days. Fixed in org.springframework.data:spring-data-rest-core 2.6.9.RELEASE, 3.0.1.RELEASE.

On this page
Malicious PATCH requests submitted to servers using Spring Data REST versions prior to 2.6.9 (Ingalls SR9), versions prior to 3.0.1 (Kay SR1) and Spring Boot versions prior to 1.5.9, 2.0 M6 can use specially crafted JSON data to run arbitrary Java code.

Severity

CVSS 3.0

9.8 critical
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
75% (unchanged from 75% a week ago; 75% 30 days ago) estimated probability of exploitation activity in the next 30 days; 100th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-20 Improper Input Validation
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2017-8046 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2017-8046?via=ask-ai-copy and https://cve.bz/cve/CVE-2017-8046?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2017-8046 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
vmware:spring_bootbefore 1.5.9
vmware:spring_boot2.0.0:milestone1
vmware:spring_boot2.0.0:milestone2
vmware:spring_boot2.0.0:milestone3
vmware:spring_boot2.0.0:milestone4
vmware:spring_boot2.0.0:milestone5
pivotal_software:spring_data_rest3.0.0
pivotal_software:spring_data_rest3.0.0:m1
pivotal_software:spring_data_rest3.0.0:m2
pivotal_software:spring_data_rest3.0.0:m3
pivotal_software:spring_data_rest3.0.0:m4
vmware:spring_data_restbefore 2.6.9
vmware:spring_data_rest3.0.0:rc1
vmware:spring_data_rest3.0.0:rc2
vmware:spring_data_rest3.0.0:rc3

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-9qf9-28h9-hqcjMavenorg.springframework.data:spring-data-rest-core<2.6.9.RELEASE2.6.9.RELEASE
GHSA-9qf9-28h9-hqcjMavenorg.springframework.data:spring-data-rest-core>=3.0.0 <3.0.1.RELEASE3.0.1.RELEASE

Red Hat

Red Hat rates this Critical.

Red Hat's statement

While there might be compatibility issues upgrading Spring REST Data independently of the Spring Boot version we recommend that customers make sure they are using a fixed version of Spring Data REST 2.6.9, or 3.0.1. RHOAR has now upgraded to version 1.5.10 of Spring Boot which is compatible with fixed versions of Spring DATA Rest.

ProductPackageStateAdvisory
Red Hat Fuse Intergration Services 2.0 based on Fuse 6.3 R7spring-bootFixed 2018-08-14RHSA-2018:2405
Red Hat OpenShift Application Runtimesspring-bootNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2017-8046.

Public exploits

Detection rules

Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-20 (51).

References

Check your stackJSON