Known Vulnerabilities for Log4j by Apache

Listed below are 8 of the newest known vulnerabilities associated with "Log4j" by "Apache".

These CVEs are retrieved based on exact matches on listed software, hardware, and vendor information (CPE data) as well as a keyword search to ensure the newest vulnerabilities with no officially listed software information are still displayed.

Data on known vulnerable versions is also displayed based on information from known CPEs

Known Vulnerabilities

CVE Shortened Description Severity Publish Date Last Modified
CVE-2022-23307 CVE-2020-9493 identified a deserialization issue that was present in Apache Chainsaw. Prior to Chainsaw V2.0 Chainsaw was a c... 8.8 - HIGH 2022-01-18 2022-07-25
CVE-2022-23305 By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a configuration parameter where the values to be inser... 9.8 - CRITICAL 2022-01-18 2022-07-25
CVE-2022-23302 JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data when the attacker has write access to... 8.8 - HIGH 2022-01-18 2022-07-25
CVE-2021-4104 JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j c... 8.8 - HIGH 2021-12-14 2022-09-07
CVE-2020-9493 A deserialization flaw was found in Apache Chainsaw versions prior to 2.1.0 which could lead to malicious code execution. 9.8 - CRITICAL 2021-06-16 2022-04-08
CVE-2020-9488 Improper validation of certificate with host mismatch in Apache Log4j SMTP appender. This could allow an SMTPS connection to ... 3.7 - LOW 2020-04-27 2022-05-12
CVE-2019-17571 Included in Log4j 1.2 is a SocketServer class that is vulnerable to deserialization of untrusted data which can be exploited ... 9.8 - CRITICAL 2019-12-20 2022-07-25
CVE-2017-5645 In Apache Log4j 2.x before 2.8.2, when using the TCP socket server or UDP socket server to receive serialized log events from... 9.8 - CRITICAL 2017-04-17 2022-04-04

Known Affected Configurations (CPE V2.3)

Type Vendor Product Version Update Edition Language

Popular searches for Log4j

Log4j – Apache Log4j 2

Log4j Apache Log4j 2 Apache Log4j 2 is an upgrade to Log4j B @ > that provides significant improvements over its predecessor, Log4j Logback while fixing some inherent problems in Logbacks architecture. The API for Log4j The Log4j F D B API supports lambda expressions. Version 2.10.0 added the module Apache Tomcat and Eclipse Jetty. Log4j Application programming interface Log file Method (computer programming) Implementation SLF4J Anonymous function Forward compatibility Class (computer programming) Apache Tomcat Jetty (web server) Programmer Modular programming Java (programming language) Plug-in (computing) Computer configuration Asynchronous I/O Application software Java version history Library (computing)

Apache log4j 1.2 -

Apache log4j 1.2 - W U SOn August 5, 2015 the Logging Services Project Management Committee announced that Log4j W U S 1.x had reached end of life. For complete text of the announcement please see the Apache Blog. See Log4j 5 3 1 1.2 is broken on Java 9 for details. Welcome to Apache og4j ! Java.

Log4j Log file Apache License Apache HTTP Server End-of-life (product) Java (programming language) Java version history Project management The Apache Software Foundation Library (computing) Statement (computer science) Application software Vulnerability (computing) Blog Data logger Source code Upgrade Common Vulnerabilities and Exposures Software license Vector (malware)

© 2022 Twitter Nitter Twitter Viewer |

Use of this information constitutes acceptance for use in an AS IS condition. There are NO warranties, implied or otherwise, with regard to this information or its use. Any use of this information is at the user's risk. It is the responsibility of user to evaluate the accuracy, completeness or usefulness of any information, opinion, advice or other content. EACH USER WILL BE SOLELY RESPONSIBLE FOR ANY consequences of his or her direct or indirect use of this web site. ALL WARRANTIES OF ANY KIND ARE EXPRESSLY DISCLAIMED. This site will NOT BE LIABLE FOR ANY DIRECT, INDIRECT or any other kind of loss.

CVE, CWE, and OVAL are registred trademarks of The MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. This site includes MITRE data granted under the following license. and Source URL Uptime Status