Homepage
About Snyk

ch.qos.reload4j:reload4j@1.2.18.0 vulnerabilities

Go back to all versions of this package
Report a new vulnerability Found a mistake?

Direct Vulnerabilities

Known vulnerabilities in the ch.qos.reload4j:reload4j package. This does not include vulnerabilities belonging to this package’s dependencies.

Automatically find and fix vulnerabilities affecting your projects. Snyk scans for vulnerabilities and provides fixes for free.
Fix for free
Vulnerability Vulnerable Version
  • H
XML External Entity (XXE) Injection

ch.qos.reload4j:reload4j is an a fork of Apache log4j version 1.2.17 with the goal of fixing pressing security issues.

Affected versions of this package are vulnerable to XML External Entity (XXE) Injection due to insufficient checks which do not disable the parsing of external general entities and external parameter entities.

How to fix XML External Entity (XXE) Injection?

Upgrade ch.qos.reload4j:reload4j to version 1.2.22 or higher.

[,1.2.22)
  • H
Deserialization of Untrusted Data

ch.qos.reload4j:reload4j is an a fork of Apache log4j version 1.2.17 with the goal of fixing pressing security issues.

Affected versions of this package are vulnerable to Deserialization of Untrusted Data. 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.

How to fix Deserialization of Untrusted Data?

Upgrade ch.qos.reload4j:reload4j to version 1.2.18.1 or higher.

[,1.2.18.1)
  • H
Deserialization of Untrusted Data

ch.qos.reload4j:reload4j is an a fork of Apache log4j version 1.2.17 with the goal of fixing pressing security issues.

Affected versions of this package are vulnerable to Deserialization of Untrusted Data. 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.

How to fix Deserialization of Untrusted Data?

Upgrade ch.qos.reload4j:reload4j to version 1.2.18.1 or higher.

[,1.2.18.1)
  • H
SQL Injection

ch.qos.reload4j:reload4j is an a fork of Apache log4j version 1.2.17 with the goal of fixing pressing security issues.

Affected versions of this package are vulnerable to SQL Injection. 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.

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

How to fix SQL Injection?

Upgrade ch.qos.reload4j:reload4j to version 1.2.18.2 or higher.

[,1.2.18.2)
  • L
Man-in-the-Middle (MitM)

ch.qos.reload4j:reload4j is an a fork of Apache log4j version 1.2.17 with the goal of fixing pressing security issues.

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 ch.qos.reload4j:reload4j to version 1.2.18.3 or higher.

[,1.2.18.3)
Go back to all versions of this package