Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

Maven package

ru.yandex.clickhouse:clickhouse-jdbc-bridge

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 8.1MavenPublished

    Using JMSAppender in log4j configuration may lead to deserialization of untrusted data

    GHSA-3w6p-8f82-gw8r

    Affected
    • Maven ru.yandex.clickhouse:clickhouse-jdbc-bridge < 2.0.7
    Fixed in
    2.0.7· Vendor fix available
    Issue
    Impact ClickHouse JDBC Bridge uses slf4j-log4j12 1.7.32, which depends on log4j 1.2.17. It allows a remote attacker to execute code on the server, if you changed default log4j configuration by adding JMSAppender and an insecure JMS broker. Patches The patch version 2.0.7 removed log4j dependency by replacing slf4j-log4j12 to slf4j-jdk14. Logging configuration is also changed from log4j.properties to logging.properties. Workarounds 1. Do NOT change log4j configuration to use JMSAppender along with insecure JMS broker 2. Alternatively, you can issue below command to remove JMSAppender.class: References Please refer to CVE-2021-4104 to read more. For more information If you have any questions or comments about this advisory, please feel free to open an issue in the repository.

    Recommended action: Upgrade to 2.0.7 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →