2.26.1
13 years ago
8 days ago
Known vulnerabilities in the org.apache.logging.log4j:log4j-core package. This does not include vulnerabilities belonging to this package’s dependencies.
Snyk's AI Trust Platform automatically finds the best upgrade path and integrates with your development workflows. Secure your code at zero cost.
Fix for free| Vulnerability | Vulnerable Version |
|---|---|
org.apache.logging.log4j:log4j-core is a logging library for Java. Affected versions of this package are vulnerable to Improper Encoding or Escaping of Output in the XmlLayout plugin. An attacker can cause log events to be silently lost or malformed by injecting XML 1.0 forbidden characters into log messages or MDC values. This may result in malformed XML output, which can cause downstream log-processing systems to drop affected records or prevent log events from being delivered to their intended destinations. How to fix Improper Encoding or Escaping of Output? A fix was pushed into the | [2.0-alpha1,2.25.4)[3.0.0-alpha1,) |
org.apache.logging.log4j:log4j-core is a logging library for Java. Affected versions of this package are vulnerable to Improper Validation of Certificate with Host Mismatch due to the lack of TLS hostname verification in the How to fix Improper Validation of Certificate with Host Mismatch? Upgrade | [,2.25.3) |
org.apache.logging.log4j:log4j-core is a logging library for Java. Affected versions of this package are vulnerable to Man-in-the-Middle (MitM). 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. How to fix Man-in-the-Middle (MitM)? Upgrade | [,2.13.2) |
org.apache.logging.log4j:log4j-core is a logging library for Java. Affected versions of this package are vulnerable to Deserialization of Untrusted Data. 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. How to fix Deserialization of Untrusted Data? Upgrade | [,2.8.2) |