Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
☕
☕ Maven
Not in CISA KEV
HIGH severity

Using JMSAppender in log4j configuration may lead to deserialization of untrusted dataGHSA-3w6p-8f82-gw8r

HIGH

GHSA-3w6p-8f82-gw8r is a high-severity (CVSS 8.1) vulnerability in ru.yandex.clickhouse:clickhouse-jdbc-bridge. A fix is available for ru.yandex.clickhouse:clickhouse-jdbc-bridge — see the affected versions and patch details below.

Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Dec 3, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
☕ru.yandex.clickhouse:clickhouse-jdbc-bridge

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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:
# install zip command if you don't have
apt-get update && apt-get install -y zip
# remove the class
zip -d clickhouse-jdbc-bridge*.jar ru/yandex/clickhouse/jdbcbridge/internal/log4j/net/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.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
☕Mavenru.yandex.clickhouse:clickhouse-jdbc-bridgeall versions2.0.7ru.yandex.clickhouse:clickhouse-jdbc-bridge:2.0.7

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for ru.yandex.clickhouse:clickhouse-jdbc-bridge, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update ru.yandex.clickhouse:clickhouse-jdbc-bridge to 2.0.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3w6p-8f82-gw8r is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

### Impact ClickHouse JDBC Bridge uses [slf4j-log4j12 1.7.32](https://repo1.maven.org/maven2/org/slf4j/slf4j-log4j12/1.7.32/), which depends on [log4j 1.2.17](https://repo1.maven.org/maven2/log4j/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 l
O3 Security · Impact-Aware SCA

Is GHSA-3w6p-8f82-gw8r in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works
Using JMSAppender in log4j configuration may lead to…