Current Description
An issue was discovered in Pivotal Spring Security 4.2.0.RELEASE through 4.2.2.RELEASE, and Spring Security 5.0.0.M1. When configured to enable default typing, Jackson contained a deserialization vulnerability that could lead to arbitrary code execution. Jackson fixed this vulnerability by blacklisting known "deserialization gadgets." Spring Security configures Jackson with global default typing enabled, which means that (through the previous exploit) arbitrary code could be executed if all of the following is true: (1) Spring Security's Jackson support is being leveraged by invoking SecurityJackson2Modules.getModules(ClassLoader) or SecurityJackson2Modules.enableDefaultTyping(ObjectMapper); (2) Jackson is used to deserialize data that is not trusted (Spring Security does not perform deserialization using Jackson, so this is an explicit choice of the user); and (3) there is an unknown (Jackson is not blacklisting it already) "deserialization gadget" that allows code execution present on the classpath. Jackson provides a blacklisting approach to protecting against this type of attack, but Spring Security should be proactive against blocking unknown "deserialization gadgets" when Spring Security enables default typing.
Source:
MITRE
Description Last Modified:
11/27/2017
View Analysis Description
Analysis Description
An issue was discovered in Pivotal Spring Security 4.2.0.RELEASE through 4.2.2.RELEASE, and Spring Security 5.0.0.M1. When configured to enable default typing, Jackson contained a deserialization vulnerability that could lead to arbitrary code execution. Jackson fixed this vulnerability by blacklisting known "deserialization gadgets." Spring Security configures Jackson with global default typing enabled, which means that (through the previous exploit) arbitrary code could be executed if all of the following is true: (1) Spring Security's Jackson support is being leveraged by invoking SecurityJackson2Modules.getModules(ClassLoader) or SecurityJackson2Modules.enableDefaultTyping(ObjectMapper); (2) Jackson is used to deserialize data that is not trusted (Spring Security does not perform deserialization using Jackson, so this is an explicit choice of the user); and (3) there is an unknown (Jackson is not blacklisting it already) "deserialization gadget" that allows code execution present on the classpath. Jackson provides a blacklisting approach to protecting against this type of attack, but Spring Security should be proactive against blocking unknown "deserialization gadgets" when Spring Security enables default typing.
Source:
MITRE
Description Last Modified:
11/27/2017
Impact
CVSS v3.0 Severity and Metrics:
Base Score:
8.1 HIGH
Vector:
AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
(V3 legend)
Impact Score:
5.9
Exploitability Score:
2.2
Attack Vector (AV):
Network
Attack Complexity (AC):
High
Privileges Required (PR):
None
User Interaction (UI):
None
Scope (S):
Unchanged
Confidentiality (C):
High
Integrity (I):
High
Availability (A):
High
CVSS v2.0 Severity and Metrics:
Base Score:
6.8 MEDIUM
Vector:
(AV:N/AC:M/Au:N/C:P/I:P/A:P)
(V2 legend)
Impact Subscore:
6.4
Exploitability Subscore:
8.6
Access Vector (AV):
Network
Access Complexity (AC):
Medium
Authentication (AU):
None
Confidentiality (C):
Partial
Integrity (I):
Partial
Availability (A):
Partial
Additional Information:
Allows unauthorized disclosure of information
Allows unauthorized modification
Allows disruption of service
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving NIST webspace. We have provided these links to other web sites because
they may have information that would be of interest to you. No inferences should be drawn on account of other sites
being referenced, or not, from this page. There may be other web sites that are more appropriate for your purpose.
NIST does not necessarily endorse the views expressed, or concur with the facts presented on these sites. Further,
NIST does not endorse any commercial products that may be mentioned on these sites. Please address comments about
this page to nvd@nist.gov.
Technical Details
Vulnerability Type
(View All)
- Deserialization of Untrusted Data (CWE-502)
Change History
2 change records found
- show changes
Initial Analysis -
12/20/2017 5:31:38 PM
| Action |
Type |
Old Value |
New Value |
| Added |
CPE Configuration |
|
OR
*cpe:2.3:a:pivotal_software:spring_security:4.2.0:release:*:*:*:*:*:*
*cpe:2.3:a:pivotal_software:spring_security:4.2.1:release:*:*:*:*:*:*
*cpe:2.3:a:pivotal_software:spring_security:4.2.2:release:*:*:*:*:*:*
*cpe:2.3:a:pivotal_software:spring_security:5.0.0:m1:*:*:*:*:*:* |
| Added |
CVSS V2 |
|
(AV:N/AC:M/Au:N/C:P/I:P/A:P) |
| Added |
CVSS V3 |
|
AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
| Added |
CWE |
|
CWE-502 |
| Changed |
Reference Type |
http://www.securityfocus.com/bid/99080 No Types Assigned |
http://www.securityfocus.com/bid/99080 Third Party Advisory, VDB Entry |
| Changed |
Reference Type |
https://pivotal.io/security/cve-2017-4995 No Types Assigned |
https://pivotal.io/security/cve-2017-4995 Issue Tracking, Vendor Advisory |
CVE Modified by MITRE -
11/27/2017 9:29:00 PM
| Action |
Type |
Old Value |
New Value |
| Added |
Reference |
|
http://www.securityfocus.com/bid/99080 [No Types Assigned] |