Spring Security OAuth up to 2.0.17/2.1.4/2.2.4/2.3.5 redirect_uri
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Spring Security OAuth up to 2.0.17/2.1.4/2.2.4/2.3.5. It has been rated as problematic. Affected by this issue is some unknown functionality. This manipulation of the argument redirect_uri causes redirect. This vulnerability appears as CVE-2019-11269. The attack may be initiated remotely. In addition, an exploit is available. Upgrading the affected component is advised.
Details
A vulnerability classified as problematic was found in Spring Security OAuth up to 2.0.17/2.1.4/2.2.4/2.3.5. Affected by this vulnerability is an unknown function. The manipulation of the argument redirect_uri with an unknown input leads to a redirect vulnerability. The CWE definition for the vulnerability is CWE-601. A web application accepts a user-controlled input that specifies a link to an external site, and uses that link in a Redirect. This simplifies phishing attacks. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
Spring Security OAuth versions 2.3 prior to 2.3.6, 2.2 prior to 2.2.5, 2.1 prior to 2.1.5, and 2.0 prior to 2.0.18, as well as older unsupported versions could be susceptible to an open redirector attack that can leak an authorization code. A malicious user or attacker can craft a request to the authorization endpoint using the authorization code grant type, and specify a manipulated redirection URI via the redirect_uri parameter. This can cause the authorization server to redirect the resource owner user-agent to a URI under the control of the attacker with the leaked authorization code.
The weakness was presented 06/12/2019 (Website). It is possible to read the advisory at pivotal.io. This vulnerability is known as CVE-2019-11269 since 04/18/2019. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. Technical details and also a public exploit are known. The attack technique deployed by this issue is T1204.001 according to MITRE ATT&CK.
It is possible to download the exploit at packetstormsecurity.com. It is declared as proof-of-concept.
Upgrading to version 2.0.18, 2.1.5, 2.2.5 or 2.3.6 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at Exploit-DB (47000). Be aware that VulDB is the high quality source for vulnerability data.
Product
Name
Version
- 2.0.0
- 2.0.1
- 2.0.2
- 2.0.3
- 2.0.4
- 2.0.5
- 2.0.6
- 2.0.7
- 2.0.8
- 2.0.9
- 2.0.10
- 2.0.11
- 2.0.12
- 2.0.13
- 2.0.14
- 2.0.15
- 2.0.16
- 2.0.17
- 2.1.0
- 2.1.1
- 2.1.2
- 2.1.3
- 2.1.4
- 2.2.0
- 2.2.1
- 2.2.2
- 2.2.3
- 2.2.4
- 2.3.0
- 2.3.1
- 2.3.2
- 2.3.3
- 2.3.4
- 2.3.5
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 6.3
VulDB Temp Score: 5.7
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.4
NVD Vector: 🔍
CNA Base Score: 4.2
CNA Vector (Pivotal Software, Inc.): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: RedirectCWE: CWE-601
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Spring Security OAuth 2.0.18/2.1.5/2.2.5/2.3.6
Timeline
04/18/2019 🔍06/12/2019 🔍
06/12/2019 🔍
12/09/2024 🔍
Sources
Advisory: 153299Status: Confirmed
Confirmation: 🔍
CVE: CVE-2019-11269 (🔍)
GCVE (CVE): GCVE-0-2019-11269
GCVE (VulDB): GCVE-100-136423
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 06/12/2019 21:45Updated: 12/09/2024 08:09
Changes: 06/12/2019 21:45 (56), 06/23/2020 16:23 (1), 10/05/2023 07:55 (4), 10/05/2023 08:01 (12), 07/02/2024 12:17 (22), 12/09/2024 08:09 (3)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.