High Oracle Retail Applications Security (Spring Framework) CVEs

Protected by Waratek 1 50.0% Rule in development 0 0.0% Mitigation candidate 0 0.0% No exploit published 1 50.0%

Critical 0 0.0% High 2 100.0% Medium 0 0.0% Low 0 0.0% None 0 0.0% Unknown 0 0.0%

blocked by ARMR today 1 50.0% partly blocked 0 0.0% not blocked 1 50.0% not established 0 0.0% unrecorded 0 0.0%

Exploited 0 0.0% Working exploit published 0 0.0% Proof of concept only 0 0.0% Forecast only 0 0.0% No public exploit 2 100.0%

split by StatusSeverityProtectionExploit maturity peak 1 / month

Dec 161 Protected by Waratek1 High1 blocked by ARMR today1 No public exploit1 Jan 170 Feb 170 Mar 170 Apr 170 May 170 Jun 170 Jul 170 Aug 170 Sep 170 Oct 170 Nov 170 Dec 170 Jan 180 Feb 180 Mar 180 Apr 180 May 181 No exploit published1 High1 not blocked1 No public exploit1

Jan 17Mar 17May 17Jul 17Sep 17Nov 17Jan 18Mar 18May 18

CVE	Severity	Published▾	Status	Exploitation	Description
CVE-2018-1258	High	2018-05-11	No exploit published	No public exploit	Spring Framework version 5.0.5 when used in combination with any versions of Spring Security contains an authorization bypass when using method security. An unauthorized malicious user can gain unauthorized access to methods that should be restricted.
CVE-2016-9878	High	2016-12-29	Protected by Waratek	No public exploit	An issue was discovered in Pivotal Spring Framework before 3.2.18, 4.2.x before 4.2.9, and 4.3.x before 4.3.5. Paths provided to the ResourceServlet were not properly sanitized and as a result exposed to directory traversal attacks.

CVE

Severity

Published▾

Status

Exploitation

Description

CVE-2018-1258

High

2018-05-11

No exploit published

No public exploit

Spring Framework version 5.0.5 when used in combination with any versions of Spring Security contains an authorization bypass when using method security. An unauthorized malicious user can gain unauthorized access to methods that should be restricted.

CVE-2016-9878

High

2016-12-29

Protected by Waratek

No public exploit

An issue was discovered in Pivotal Spring Framework before 3.2.18, 4.2.x before 4.2.9, and 4.3.x before 4.3.5. Paths provided to the ResourceServlet were not properly sanitized and as a result exposed to directory traversal attacks.