Oracle Critical Patch Update October 2020 CVEs

VRT 391,192 CVEs tracked · 15,442 in RASP scope · data as of 17 hours ago

Description contains RASP scope Status Exploitation Severity

Reset

Overview 1 match, all in RASP scope, all protected, all public PoC, all EPSS ≥ 0.5 · 0 KEV · 0 CISA SSVC · 0 disputed

1match, all in RASP scope, all protected, all public PoC, all EPSS ≥ 0.5 0KEV0.0% 0CISA SSVC0.0% 0disputed0.0%

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

Protected by RASP 1 100.0% Rule in development 0 0.0% Mitigation candidate 0 0.0% No exploit published 0 0.0% No fix identified 0 0.0% Mitigated by environment configuration 0 0.0% Queued for review 0 0.0% Not applicable 0 0.0% Out of RASP scope 0 0.0% Rejected 0 0.0%

blocked by ARMR today 1 100.0% not blocked 0 0.0% not established 0 0.0% unrecorded 0 0.0%

Exploited in the wild 0 0.0% Working exploit published 1 100.0% Proof of concept only 0 0.0% Forecast only 0 0.0% No public exploit 0 0.0%

split by SeverityStatusProtectionExploit maturity peak 1 / month

Mar 19

1 match CSV JSON

CVE	Severity	Published▾	Status	Exploitation	Description
CVE-2019-0192	Critical	2019-03-07	Protected by RASP	Working exploit published	In Apache Solr versions 5.0.0 to 5.5.5 and 6.0.0 to 6.6.5, the Config API allows to configure the JMX server via an HTTP POST request. By pointing it to a malicious RMI server, an attacker could take advantage of Solr's unsafe deserialization to trigger remote code execution on the Solr side.

CVE

Severity

Published▾

Status

Exploitation

Description

CVE-2019-0192

Critical

2019-03-07

Protected by RASP

Working exploit published

In Apache Solr versions 5.0.0 to 5.5.5 and 6.0.0 to 6.6.5, the Config API allows to configure the JMX server via an HTTP POST request. By pointing it to a malicious RMI server, an attacker could take advantage of Solr's unsafe deserialization to trigger remote code execution on the Solr side.