p PatchFirst

PatchFirst · Latest vulnerabilities

apache-log4j1.2 vulnerabilities

Vulnerabilities published for apache-log4j1.2 in the last 30 days: 0. Listed in the KEV catalogue: 0.

Filter vulnerabilities
Clear filters

Vulnerabilities: 6

  1. CVE-2026-34480

    Medium · CVSS 6.9EPSS 1.06%No fix published

    Apache Log4j Core: Silent log event loss in XmlLayout due to unescaped XML 1.0 forbidden characters

    Apache Log4j Core's XmlLayout https://logging.apache.org/log4j/2.x/manual/layouts.html#XmlLayout , in versions up to and including 2.25.3, fails to sanitize characters forbidden by the XML 1.0 specification https://www.w3.org/TR/xml/#charsets producing invalid XML output whenever a log message or MDC value contains such characters. The impact depends on the StAX implementation in use: * JRE built-in StAX: Forbidden characters are silently written to the output, producing malformed XML. Conforming parsers must reject such documents with a fatal error, which may cause downstream log-processing systems to drop the affected records. *

    Published Updated
  2. CVE-2022-23305

    Critical · CVSS 9.8EPSS 66.54%Fix available

    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 fur

    • Update to 1.2.17-11
    Published Updated
  3. CVE-2022-23302

    High · CVSS 8.8EPSS 63.84%Fix available

    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 iss

    • Update to 1.2.17-11
    Published Updated
  4. CVE-2021-4104

    High · CVSS 7.5EPSS 80.6%Fix available

    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.

    • Update to 1.2.17-11
    Published Updated
  5. CVE-2019-17571

    Critical · CVSS 9.8EPSS 69.98%Fix available

    CVE-2019-17571

    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 up to 1.2 up to 1.2.17.

    • Update to 1.2.17-9
    Published Updated

Check your server

Check your installed stack and versions against the current vulnerability feeds.

Check your server →