cve,link,title,description,vendor,products,score,severity,epss,cisa,cisa_published,article,ransomware,exploited,exploited_date,poc,trended,trended_no_1,trended_no_1_date,published,trended_score
CVE-2023-26464,https://securityvulnerability.io/vulnerability/CVE-2023-26464,Apache Log4j 1.x (EOL) allows DoS in Chainsaw and SocketAppender,"An improper deserialization of a specially crafted deeply nested hashmap or hashtable in the Chainsaw or SocketAppender components of Apache Log4j 1.x can lead to exhaustion of available memory in the Java Virtual Machine (JVM). This vulnerability arises when the components operate on JRE versions prior to 1.7, allowing attackers to craft logging entries that exploit this issue effectively. Affected systems are strongly advised to upgrade to Log4j 2.x, as the existing versions have reached the end of their support lifecycle.",Apache,Apache Log4j,7.5,HIGH,0.0014900000533089042,false,,false,false,false,,,false,false,,2023-03-10T14:15:00.000Z,0
CVE-2022-23307,https://securityvulnerability.io/vulnerability/CVE-2022-23307," A deserialization flaw in the Chainsaw component of Log4j 1 can lead to malicious code execution.",CVE-2020-9493 identified a deserialization issue that was present in Apache Chainsaw. Prior to Chainsaw V2.0 Chainsaw was a component of Apache Log4j 1.2.x where the same issue exists.,Apache,Apache Log4j 1.x,8.8,HIGH,0.004819999914616346,false,,false,false,false,,,false,false,,2022-01-18T15:25:23.000Z,0
CVE-2022-23305,https://securityvulnerability.io/vulnerability/CVE-2022-23305,SQL injection in JDBC Appender in Apache Log4j V1,"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.",Apache,Apache Log4j 1.x,9.8,CRITICAL,0.003650000086054206,false,,false,false,true,2023-07-24T18:52:15.000Z,true,false,false,,2022-01-18T15:25:22.000Z,0
CVE-2022-23302,https://securityvulnerability.io/vulnerability/CVE-2022-23302,Deserialization of untrusted data in JMSSink in Apache Log4j 1.x,"JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration or if the configuration references an LDAP service the attacker has access to. The attacker can provide a TopicConnectionFactoryBindingName configuration causing JMSSink to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-4104. Note this issue only affects Log4j 1.x when specifically configured to use JMSSink, which is not the default. 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.",Apache,Apache Log4j 1.x,8.8,HIGH,0.07632999867200851,false,,false,false,false,,,false,false,,2022-01-18T15:25:20.000Z,0
CVE-2021-45046,https://securityvulnerability.io/vulnerability/CVE-2021-45046,Apache Log4j2 Thread Context Message Pattern and Context Lookup Pattern vulnerable to a denial of service attack,"It was found that the fix to address CVE-2021-44228 in Apache Log4j 2.15.0 was incomplete in certain non-default configurations. This could allows attackers with control over Thread Context Map (MDC) input data when the logging configuration uses a non-default Pattern Layout with either a Context Lookup (for example, $${ctx:loginId}) or a Thread Context Map pattern (%X, %mdc, or %MDC) to craft malicious input data using a JNDI Lookup pattern resulting in an information leak and remote code execution in some environments and local code execution in all environments. Log4j 2.16.0 (Java 8) and 2.12.2 (Java 7) fix this issue by removing support for message lookup patterns and disabling JNDI functionality by default.",Apache,Apache Log4j,9,CRITICAL,0.9666799902915955,true,2023-05-01T00:00:00.000Z,false,true,true,2021-12-24T09:02:55.000Z,true,false,false,,2021-12-14T16:55:09.000Z,0
CVE-2021-4104,https://securityvulnerability.io/vulnerability/CVE-2021-4104,Deserialization of untrusted data in JMSAppender in Apache Log4j 1.2,"JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration. The attacker can provide TopicBindingName and TopicConnectionFactoryBindingName configurations causing JMSAppender to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-44228. Note this issue only affects Log4j 1.2 when specifically configured to use JMSAppender, which is not the default. 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.",Apache,Apache Log4j 1.x,7.5,HIGH,0.11892999708652496,false,,false,false,true,2022-01-10T09:01:46.000Z,true,false,false,,2021-12-14T00:00:00.000Z,0
CVE-2020-9488,https://securityvulnerability.io/vulnerability/CVE-2020-9488,,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,Apache,Apache Log4j,3.7,LOW,0.0020099999383091927,false,,false,false,false,,,false,false,,2020-04-27T15:36:10.000Z,0
CVE-2017-5645,https://securityvulnerability.io/vulnerability/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 another application, a specially crafted binary payload can be sent that, when deserialized, can execute arbitrary code.",Apache,Apache Log4j,9.8,CRITICAL,0.9212599992752075,false,,false,false,true,2021-12-14T22:27:14.000Z,true,false,false,,2017-04-17T21:00:00.000Z,0