p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in apache-log4j1.2

In den letzten 30 Tagen veröffentlichte Sicherheitslücken für apache-log4j1.2: 0. Davon im KEV-Katalog: 0.

Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 6

  1. CVE-2026-34480

    Mittel · CVSS 6.9EPSS 1,06%Keine Korrektur veröffentlicht

    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. *

    Veröffentlicht Aktualisiert
  2. CVE-2022-23307

    Hoch · CVSS 8.8EPSS 54,41%Korrektur verfügbar

    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.

    • Auf 1.2.17-11 aktualisieren
    Veröffentlicht Aktualisiert
  3. CVE-2022-23305

    Kritisch · CVSS 9.8EPSS 66,54%Korrektur verfügbar

    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

    • Auf 1.2.17-11 aktualisieren
    Veröffentlicht Aktualisiert
  4. CVE-2022-23302

    Hoch · CVSS 8.8EPSS 63,84%Korrektur verfügbar

    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

    • Auf 1.2.17-11 aktualisieren
    Veröffentlicht Aktualisiert
  5. CVE-2021-4104

    Hoch · CVSS 7.5EPSS 80,6%Korrektur verfügbar

    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.

    • Auf 1.2.17-11 aktualisieren
    Veröffentlicht Aktualisiert
  6. CVE-2019-17571

    Kritisch · CVSS 9.8EPSS 69,98%Korrektur verfügbar

    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.

    • Auf 1.2.17-9 aktualisieren
    Veröffentlicht Aktualisiert

Prüfen Sie Ihren Server

Gleichen Sie Ihren installierten Stack und seine Versionen mit den aktuellen Sicherheitsmeldungen ab.

Prüfen Sie Ihren Server →