WaratekVRT Sign in
Reset
More filters (1)
Columns
Including CVEs outside Waratek scope✕Oracle product: Oracle Fusion Middleware / Core (Apache Log4j)✕
Overview 3 matches · 2 in Waratek scope · 2 protected · 1 exploited · 0 CISA KEV · 2 public PoC · 2 EPSS ≥ 0.5
3matches 2in Waratek scope66.7% 2protected66.7% 1exploited33.3% 0CISA KEV0.0% 2public PoC66.7% 2EPSS ≥ 0.566.7%
Protected by Waratek 2 66.7% Rule in development 0 0.0% Mitigation candidate 0 0.0% No exploit published 0 0.0% Outside Waratek scope 1 33.3% Not applicable 0 0.0% Withdrawn CVE 0 0.0%
Critical 1 33.3% High 0 0.0% Medium 1 33.3% Low 1 33.3% None 0 0.0% Unknown 0 0.0%
blocked by ARMR today 2 66.7% partly blocked 0 0.0% not blocked 1 33.3% not established 0 0.0% unrecorded 0 0.0%
Exploited 1 33.3% Working exploit published 0 0.0% Proof of concept only 1 33.3% Forecast only 0 0.0% No public exploit 1 33.3%
split by peak 1 / quarter
Outside Waratek scope: 1Protected by Waratek: 2 Low: 1Medium: 1Critical: 1 not blocked: 1blocked by ARMR today: 2 No public exploit: 1Proof of concept only: 1Exploited: 1
Q2 201 Outside Waratek scope1 Low1 not blocked1 No public exploit1 Q3 200 Q4 200 Q1 210 Q2 210 Q3 210 Q4 211 Protected by Waratek1 Medium1 blocked by ARMR today1 Exploited1 Q1 221 Protected by Waratek1 Critical1 blocked by ARMR today1 Proof of concept only1
Q2 20Q3 20Q4 20Q1 21Q2 21Q3 21Q4 21Q1 22
3 matches Sign in to download these CVEs as CSV or JSON, or to follow them in a feed.
CVE Severity Published▾ Status Exploitation Description
CVE-2022-23305 Critical 2022-01-18 Protected by Waratek Proof of concept only By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a configuration parameter where the values to be inserted are converters from PatternLayout. The message converter, %m, is likely to always be included. This allows attackers to manipulate the SQL by entering crafted strings into input fields or headers of an application that are logged allowing unintended SQL queries to be executed. Note this issue only affects Log4j 1.x when specifically configured to use the JDBCAppender, which is not the default. Beginning in version 2.0-beta8, the JDBCAppender was re-introduced with proper support for parameterized SQL queries and further customization over the columns written to in logs. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.
CVE-2021-45105 Medium 2021-12-18 Protected by Waratek Exploited Apache Log4j2 versions 2.0-alpha1 through 2.16.0 (excluding 2.12.3 and 2.3.1) did not protect from uncontrolled recursion from self-referential lookups. This allows an attacker with control over Thread Context Map data to cause a denial of service when a crafted string is interpreted. This issue was fixed in Log4j 2.17.0, 2.12.3, and 2.3.1.
CVE-2020-9488 Low 2020-04-27 Outside Waratek scope No public exploit Improper validation of certificate with host mismatch in Apache Log4j SMTP appender. This could allow an SMTPS connection to be intercepted by a man-in-the-middle attack which could leak any log messages sent through that appender. Fixed in Apache Log4j 2.12.3 and 2.13.1