VRT 391,810 CVEs tracked · 15,472 in RASP scope · data as of 49 minutes ago
Reset
More filters (3)
Columns
Published from 2020-02-01✕Published to 2020-02-29✕CISA: exploit demonstrated✕
Overview 2 matches, all in RASP scope, all CISA SSVC · 1 protected · 1 KEV · 1 public PoC · 1 EPSS ≥ 0.5 · 0 disputed
2matches, all in RASP scope, all CISA SSVC 1protected50.0% 1KEV50.0% 1public PoC50.0% 1EPSS ≥ 0.550.0% 0disputed0.0%
Critical 1 50.0% High 1 50.0% Medium 0 0.0% Low 0 0.0% None 0 0.0% Unknown 0 0.0%
Protected by RASP 1 50.0% Rule in development 0 0.0% Mitigation candidate 0 0.0% No exploit published 1 50.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 50.0% not blocked 1 50.0% not established 0 0.0% unrecorded 0 0.0%
Exploited in the wild 1 50.0% Working exploit published 0 0.0% Proof of concept only 1 50.0% Forecast only 0 0.0% No public exploit 0 0.0%
split by peak 2 / month
Unknown: 0None: 0Low: 0Medium: 0High: 1Critical: 1 Rejected: 0Out of RASP scope: 0Not applicable: 0Queued for review: 0Mitigated by environment configuration: 0No fix identified: 0No exploit published: 1Mitigation candidate: 0Rule in development: 0Protected by RASP: 1 unrecorded: 0not established: 0not blocked: 1blocked by ARMR today: 1 No public exploit: 0Forecast only: 0Proof of concept only: 1Working exploit published: 0Exploited in the wild: 1 February 2020: 2 CVEs
Feb 20
2 matches CSV JSON
CVE Severity Published▾ Status Exploitation Description
CVE-2020-5245 High 2020-02-24 No exploit published Proof of concept only Dropwizard-Validation before 1.3.19, and 2.0.2 may allow arbitrary code execution on the host system, with the privileges of the Dropwizard service account, by injecting arbitrary Java Expression Language expressions when using the self-validating feature. The issue has been fixed in dropwizard-validation 1.3.19 and 2.0.2.
CVE-2020-1938 Critical 2020-02-24 Protected by RASP Exploited in the wild When using the Apache JServ Protocol (AJP), care must be taken when trusting incoming connections to Apache Tomcat. Tomcat treats AJP connections as having higher trust than, for example, a similar HTTP connection. If such connections are available to an attacker, they can be exploited in ways that may be surprising. In Apache Tomcat 9.0.0.M1 to 9.0.0.30, 8.5.0 to 8.5.50 and 7.0.0 to 7.0.99, Tomcat shipped with an AJP Connector enabled by default that listened on all configured IP addresses. It was expected (and recommended in the security guide) that this Connector would be disabled if not required. This vulnerability report identified a mechanism that allowed: - returning arbitrary files from anywhere in the web application - processing any file in the web application as a JSP Further, if the web application allowed file upload and stored those files within the web application (or the attacker was able to control the content of the web application by some other means) then this, along with the ability to process a file as a JSP, made remote code execution possible. It is important to note that mitigation is only required if an AJP port is accessible to untrusted users. Users wishing to take a defence-in-depth approach and block the vector that permits returning arbitrary files and execution as JSP may upgrade to Apache Tomcat 9.0.31, 8.5.51 or 7.0.100 or later. A number of changes were made to the default AJP Connector configuration in 9.0.31 to harden the default configuration. It is likely that users upgrading to 9.0.31, 8.5.51 or 7.0.100 or later will need to make small changes to their configurations.