CVE-2016-4977
When processing authorization requests using the whitelabel views in Spring Security OAuth 2.0.0 to 2.0.9 and 1.0.0 to 1.0.5, the response_type parameter value was executed as Spring SpEL which enabled a malicious user to trigger remote code execution via the crafting of the value for response_type.
Published : 2017-05-25 17:29 Updated : 2019-10-16 11:15
CVSS Score
More info
Score 6.5 / 10
A vulnerability exploitable with network access means the vulnerable software is bound to the network stack and the attacker does not require local network access or local access. Such a vulnerability is often termed "remotely exploitable". An example of a network attack is an RPC buffer overflow.
Specialized access conditions or extenuating circumstances do not exist. The following are examples:
- The affected product typically requires access to a wide range of systems and users, possibly anonymous and untrusted (e.g., Internet-facing web or mail server).
- The affected configuration is default or ubiquitous.
- The attack can be performed manually and requires little skill or additional information gathering.
- The race condition is a lazy one (i.e., it is technically a race but easily winnable).
The vulnerability requires an attacker to be logged into the system (such as at a command line or via a desktop session or web interface).
There is considerable informational disclosure. Access to some system files is possible, but the attacker does not have control over what is obtained, or the scope of the loss is constrained. An example is a vulnerability that divulges only certain tables in a database.
Modification of some system files or information is possible, but the attacker does not have control over what can be modified, or the scope of what the attacker can affect is limited. For example, system or application files may be overwritten or modified, but either the attacker has no control over which files are affected or the attacker can modify files within only a limited context or scope.
There is reduced performance or interruptions in resource availability. An example is a network-based flood attack that permits a limited number of successful connections to an Internet service.
| Vendor | Product | Version | URI |
|---|---|---|---|
| Pivotal | Spring Security Oauth | 1.0.3 | cpe:/a:pivotal:spring_security_oauth:1.0.3 |
| Pivotal | Spring Security Oauth | 2.0.4 | cpe:/a:pivotal:spring_security_oauth:2.0.4 |
| Pivotal | Spring Security Oauth | 1.0.0 | cpe:/a:pivotal:spring_security_oauth:1.0.0 |
| Pivotal | Spring Security Oauth | 2.0.5 | cpe:/a:pivotal:spring_security_oauth:2.0.5 |
| Pivotal | Spring Security Oauth | 1.0.5 | cpe:/a:pivotal:spring_security_oauth:1.0.5 |
| Pivotal | Spring Security Oauth | 2.0.2 | cpe:/a:pivotal:spring_security_oauth:2.0.2 |
| Pivotal | Spring Security Oauth | 1.0.2 | cpe:/a:pivotal:spring_security_oauth:1.0.2 |
| Pivotal | Spring Security Oauth | 2.0.0 | cpe:/a:pivotal:spring_security_oauth:2.0.0 |
| Pivotal | Spring Security Oauth | 2.0.1 | cpe:/a:pivotal:spring_security_oauth:2.0.1 |
| Pivotal | Spring Security Oauth | 1.0.1 | cpe:/a:pivotal:spring_security_oauth:1.0.1 |
| Pivotal | Spring Security Oauth | 2.0.7 | cpe:/a:pivotal:spring_security_oauth:2.0.7 |
| Pivotal | Spring Security Oauth | 2.0.3 | cpe:/a:pivotal:spring_security_oauth:2.0.3 |
| Pivotal | Spring Security Oauth | 2.0.8 | cpe:/a:pivotal:spring_security_oauth:2.0.8 |
| Pivotal | Spring Security Oauth | 1.0.4 | cpe:/a:pivotal:spring_security_oauth:1.0.4 |
| Pivotal | Spring Security Oauth | 2.0.9 | cpe:/a:pivotal:spring_security_oauth:2.0.9 |
| Pivotal | Spring Security Oauth | 2.0.6 | cpe:/a:pivotal:spring_security_oauth:2.0.6 |
-
Pivotal (1) Search CVE
-
Spring Security Oauth (16) Search CVE
-
1.0.3
-
2.0.4
-
1.0.0
-
2.0.5
-
1.0.5
-
2.0.2
-
1.0.2
-
2.0.0
-
2.0.1
-
1.0.1
-
2.0.7
-
2.0.3
-
2.0.8
-
1.0.4
-
2.0.9
-
2.0.6
-
-
References
History of changes
| Date | Event | ||
|---|---|---|---|
| 2019-10-16 11:15 | |||
| 2017-06-08 18:27 |
1 changed
16 added
|
||
| 2017-05-25 17:29 |
New CVE |