Vulnerabilities

 2 via 17 paths

Dependencies

 24

Source

 GitHub

Commit

 45e795e7

Find, fix and prevent vulnerabilities in your code.

Test and protect my applications
Severity
  • 1
  • 1
Status
  • 2
  • 0
  • 0

medium severity

Arbitrary Code Execution

  • Vulnerable module: org.apache.logging.log4j:log4j-core
  • Introduced through: org.apache.logging.log4j:log4j-core@2.17.0 and org.apache.logging.log4j:log4j-slf4j-impl@2.17.0

Detailed paths

  • Introduced through: mysql-time-machine/replicator@mysql-time-machine/replicator#45e795e7ff08643340ee5579cdcca1f30e9c4d4c › org.apache.logging.log4j:log4j-core@2.17.0
    Remediation: Upgrade to org.apache.logging.log4j:log4j-core@2.17.1.
  • Introduced through: mysql-time-machine/replicator@mysql-time-machine/replicator#45e795e7ff08643340ee5579cdcca1f30e9c4d4c › org.apache.logging.log4j:log4j-slf4j-impl@2.17.0 › org.apache.logging.log4j:log4j-core@2.17.0
    Remediation: Upgrade to org.apache.logging.log4j:log4j-slf4j-impl@2.17.1.

Overview

org.apache.logging.log4j:log4j-core is a logging library for Java.

Affected versions of this package are vulnerable to Arbitrary Code Execution.
Note: Even though this vulnerability appears to be related to the log4Shell vulnerability, this vulnerability requires an attacker to have access to modify configurations to be exploitable, which is rarely possible.

An attacker with access to modification of logging configuration is able to configure JDBCAppender with a data source referencing a JNDI URI - which can execute malicious code.

In the fixed versions, JDBCAppender is using JndiManager and disables JNDI lookups by default (via log4j2.enableJndiJdbc=false).

Alternative Remediation

If you have reason to believe your application may be vulnerable and upgrading is not an option, you can either:

  • Disable/remove JDBCAppender
  • If JDBCAppender is used, make sure that it is not configured to use any protocol other than Java

Remediation

Upgrade org.apache.logging.log4j:log4j-core to version 2.3.2, 2.12.4, 2.17.1 or higher.

References

Arbitrary Code Execution vulnerability report

low severity

Information Exposure

  • Vulnerable module: junit:junit
  • Introduced through: org.apache.logging.log4j:log4j-jul@2.17.0, org.apache.logging.log4j:log4j-1.2-api@2.17.0 and others

Detailed paths

  • Introduced through: mysql-time-machine/replicator@mysql-time-machine/replicator#45e795e7ff08643340ee5579cdcca1f30e9c4d4c › org.apache.logging.log4j:log4j-jul@2.17.0 › junit:junit@4.12
    Remediation: Upgrade to org.apache.logging.log4j:log4j-jul@2.17.0.
  • Introduced through: mysql-time-machine/replicator@mysql-time-machine/replicator#45e795e7ff08643340ee5579cdcca1f30e9c4d4c › org.apache.logging.log4j:log4j-1.2-api@2.17.0 › org.junit.vintage:junit-vintage-engine@5.7.2 › junit:junit@4.12
    Remediation: Upgrade to org.apache.logging.log4j:log4j-1.2-api@2.17.0.
  • Introduced through: mysql-time-machine/replicator@mysql-time-machine/replicator#45e795e7ff08643340ee5579cdcca1f30e9c4d4c › org.apache.logging.log4j:log4j-core@2.17.0 › org.junit.vintage:junit-vintage-engine@5.7.2 › junit:junit@4.12
    Remediation: Upgrade to org.apache.logging.log4j:log4j-core@2.17.0.
  • Introduced through: mysql-time-machine/replicator@mysql-time-machine/replicator#45e795e7ff08643340ee5579cdcca1f30e9c4d4c › org.apache.logging.log4j:log4j-slf4j-impl@2.17.0 › org.junit.vintage:junit-vintage-engine@5.7.2 › junit:junit@4.12
    Remediation: Upgrade to org.apache.logging.log4j:log4j-slf4j-impl@2.17.0.
  • Introduced through: mysql-time-machine/replicator@mysql-time-machine/replicator#45e795e7ff08643340ee5579cdcca1f30e9c4d4c › org.apache.logging.log4j:log4j-1.2-api@2.17.0 › org.apache.logging.log4j:log4j-api@2.17.0 › org.junit.jupiter:junit-jupiter-migrationsupport@5.7.2 › junit:junit@4.12
    Remediation: Upgrade to org.apache.logging.log4j:log4j-1.2-api@2.17.0.
  • Introduced through: mysql-time-machine/replicator@mysql-time-machine/replicator#45e795e7ff08643340ee5579cdcca1f30e9c4d4c › org.apache.logging.log4j:log4j-core@2.17.0 › org.apache.logging.log4j:log4j-api@2.17.0 › org.junit.jupiter:junit-jupiter-migrationsupport@5.7.2 › junit:junit@4.12
    Remediation: Upgrade to org.apache.logging.log4j:log4j-core@2.17.0.
  • Introduced through: mysql-time-machine/replicator@mysql-time-machine/replicator#45e795e7ff08643340ee5579cdcca1f30e9c4d4c › org.apache.logging.log4j:log4j-jul@2.17.0 › org.apache.logging.log4j:log4j-api@2.17.0 › org.junit.jupiter:junit-jupiter-migrationsupport@5.7.2 › junit:junit@4.12
    Remediation: Upgrade to org.apache.logging.log4j:log4j-jul@2.17.0.
  • Introduced through: mysql-time-machine/replicator@mysql-time-machine/replicator#45e795e7ff08643340ee5579cdcca1f30e9c4d4c › org.apache.logging.log4j:log4j-slf4j-impl@2.17.0 › org.apache.logging.log4j:log4j-api@2.17.0 › org.junit.jupiter:junit-jupiter-migrationsupport@5.7.2 › junit:junit@4.12
    Remediation: Upgrade to org.apache.logging.log4j:log4j-slf4j-impl@2.17.0.
  • Introduced through: mysql-time-machine/replicator@mysql-time-machine/replicator#45e795e7ff08643340ee5579cdcca1f30e9c4d4c › org.apache.logging.log4j:log4j-1.2-api@2.17.0 › org.apache.logging.log4j:log4j-api@2.17.0 › org.junit.vintage:junit-vintage-engine@5.7.2 › junit:junit@4.12
    Remediation: Upgrade to org.apache.logging.log4j:log4j-1.2-api@2.17.0.
  • Introduced through: mysql-time-machine/replicator@mysql-time-machine/replicator#45e795e7ff08643340ee5579cdcca1f30e9c4d4c › org.apache.logging.log4j:log4j-core@2.17.0 › org.apache.logging.log4j:log4j-api@2.17.0 › org.junit.vintage:junit-vintage-engine@5.7.2 › junit:junit@4.12
    Remediation: Upgrade to org.apache.logging.log4j:log4j-core@2.17.0.
  • Introduced through: mysql-time-machine/replicator@mysql-time-machine/replicator#45e795e7ff08643340ee5579cdcca1f30e9c4d4c › org.apache.logging.log4j:log4j-jul@2.17.0 › org.apache.logging.log4j:log4j-api@2.17.0 › org.junit.vintage:junit-vintage-engine@5.7.2 › junit:junit@4.12
    Remediation: Upgrade to org.apache.logging.log4j:log4j-jul@2.17.0.
  • Introduced through: mysql-time-machine/replicator@mysql-time-machine/replicator#45e795e7ff08643340ee5579cdcca1f30e9c4d4c › org.apache.logging.log4j:log4j-slf4j-impl@2.17.0 › org.apache.logging.log4j:log4j-api@2.17.0 › org.junit.vintage:junit-vintage-engine@5.7.2 › junit:junit@4.12
    Remediation: Upgrade to org.apache.logging.log4j:log4j-slf4j-impl@2.17.0.
  • Introduced through: mysql-time-machine/replicator@mysql-time-machine/replicator#45e795e7ff08643340ee5579cdcca1f30e9c4d4c › org.apache.logging.log4j:log4j-slf4j-impl@2.17.0 › org.apache.logging.log4j:log4j-core@2.17.0 › org.junit.vintage:junit-vintage-engine@5.7.2 › junit:junit@4.12
    Remediation: Upgrade to org.apache.logging.log4j:log4j-slf4j-impl@2.17.0.
  • Introduced through: mysql-time-machine/replicator@mysql-time-machine/replicator#45e795e7ff08643340ee5579cdcca1f30e9c4d4c › org.apache.logging.log4j:log4j-slf4j-impl@2.17.0 › org.apache.logging.log4j:log4j-core@2.17.0 › org.apache.logging.log4j:log4j-api@2.17.0 › org.junit.jupiter:junit-jupiter-migrationsupport@5.7.2 › junit:junit@4.12
    Remediation: Upgrade to org.apache.logging.log4j:log4j-slf4j-impl@2.17.0.
  • Introduced through: mysql-time-machine/replicator@mysql-time-machine/replicator#45e795e7ff08643340ee5579cdcca1f30e9c4d4c › org.apache.logging.log4j:log4j-slf4j-impl@2.17.0 › org.apache.logging.log4j:log4j-core@2.17.0 › org.apache.logging.log4j:log4j-api@2.17.0 › org.junit.vintage:junit-vintage-engine@5.7.2 › junit:junit@4.12
    Remediation: Upgrade to org.apache.logging.log4j:log4j-slf4j-impl@2.17.0.

Overview

junit:junit is an unit testing framework for Java

Affected versions of this package are vulnerable to Information Exposure. The JUnit4 test rule TemporaryFolder contains a local information disclosure vulnerability. On Unix like systems, the system's temporary directory is shared between all users on that system. Because of this, when files and directories are written into this directory they are, by default, readable by other users on that same system.

Note: This vulnerability does not allow other users to overwrite the contents of these directories or files. This only affects Unix like systems.

Remediation

Upgrade junit:junit to version 4.13.1 or higher.

References

Information Exposure vulnerability report