VulnerableCode Package Details - pkg:deb/debian/apache-log4j1.2@1.2.17-7%2Bdeb9u1

Search for packages

Vulnerability	Summary	Fixed by
VCID-1vfk-arae-ubha Aliases: CVE-2022-23302 GHSA-w9p3-5cr8-m3jj	Deserialization of Untrusted Data in 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.	1.2.17-10+deb11u1 Affected by 0 other vulnerabilities.
VCID-698m-2hju-2qcv Aliases: CVE-2021-4104 GHSA-fp5r-v3w9-4333	Deserialization of Untrusted Data JMSAppender in Log4j 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 when specifically configured to use JMSAppender, which is not the default. Apache Log4j reached end of life in August Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.	1.2.17-10+deb11u1 Affected by 0 other vulnerabilities.
VCID-9k99-jzq8-fyge Aliases: CVE-2022-23305 GHSA-65fg-84f6-3jq3	Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') By design, the JDBCAppender in Log4j 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 when specifically configured to use the JDBCAppender, which is not the default. Beginning, the JDBCAppender was re-introduced with proper support for parameterized SQL queries and further customization over the columns written to in logs. Apache Log4j reached end of life in August Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.	1.2.17-10+deb11u1 Affected by 0 other vulnerabilities.
VCID-bbq3-tx7c-yucn Aliases: CVE-2022-23307 GHSA-f7vh-qwp3-x37m	This advisory has been marked as False Positive and removed.	1.2.17-10+deb11u1 Affected by 0 other vulnerabilities.
VCID-zbwq-f71w-jqhy Aliases: CVE-2019-17571 GHSA-2qrg-x229-3v8q	Deserialization of Untrusted Data in Log4j Included in Log4j 1.2 is a SocketServer class that is vulnerable to deserialization of untrusted data which can be exploited to remotely execute arbitrary code when combined with a deserialization gadget when listening to untrusted network traffic for log data. This affects Log4j versions 1.2 up to 1.2.17. Users are advised to migrate to `org.apache.logging.log4j:log4j-core`.	1.2.17-8+deb10u2 Affected by 5 other vulnerabilities. This version is affected by these other vulnerabilities: {{ fixed_by_vuln.vulnerability_id }} {{ fixed_by_vuln.vulnerability_id }} {{ fixed_by_vuln.vulnerability_id }} {{ fixed_by_vuln.vulnerability_id }} {{ fixed_by_vuln.vulnerability_id }} 1.2.17-10+deb11u1 Affected by 0 other vulnerabilities.

Vulnerability

Summary

Fixed by

VCID-1vfk-arae-ubha
Aliases:
CVE-2022-23302
GHSA-w9p3-5cr8-m3jj

Deserialization of Untrusted Data in 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.