CVE-2018-15758
No exploitation reported by the sources we read.
- Published2018-10-18
- Fixed in2.3.4 · 2.2.3 · 2.1.3 · 2.0.16
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
Spring Security OAuth, versions 2.3 prior to 2.3.4, and 2.2 prior to 2.2.3, and 2.1 prior to 2.1.3, and 2.0 prior to 2.0.16, and older unsupported versions could be susceptible to a privilege escalation under certain conditions. A malicious user or attacker can craft a request to the approval endpoint that can modify the previously saved authorization request and lead to a privilege escalation on the subsequent approval. This scenario can happen if the application is configured to use a custom approval endpoint that declares AuthorizationRequest as a controller method argument. This vulnerability exposes applications that meet all of the following requirements: Act in the role of an Authorization Server (e.g. @EnableAuthorizationServer) and use a custom Approval Endpoint that declares AuthorizationRequest as a controller method argument. This vulnerability does not expose applications that: Act in the role of an Authorization Server and use the default Approval Endpoint, act in the role of a Resource Server only (e.g. @EnableResourceServer), act in the role of a Client only (e.g. @EnableOAuthClient).
Timeline
dates in UTC- 2018-10-1822:29CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 18:48 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2018-15758?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2018-15758?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 2.3 | ≥ 2.3.0, < 2.3.4 | 2.3.4 | NVD |
| 2.2 | ≥ 2.2.0, < 2.2.3 | 2.2.3 | NVD |
| 2.1 | ≥ 2.1.0, < 2.1.3 | 2.1.3 | NVD |
| 2.0 | ≥ 2.0.0, < 2.0.16 | 2.0.16 | NVD |
| 1.0 | ≤ 1.0.5 | no fix published | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
- Update Pivotal software spring security oauth to 2.3.4 · 2.2.3 · 2.1.3 · 2.0.16
Advisories and patches
- pivotal.ioMitigation · Vendor Advisory
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
- CNACVSS 3.09.6read 2026-10-23
- NVDCVSS 3.08.1read 2026-10-23
- NVDCVSS 2.06.8read 2026-10-23
- FIRST EPSSEPSS score2.2 %2026-10-22
Technical details
- CVSS v3 Vector
- CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
- Published
- 2018-10-18
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2018-15758?
Is CVE-2018-15758 actively exploited?
What is the CVSS score for CVE-2018-15758?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.