Advisory record · GHSA-3w6p-8f82-gw8r

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

CVSS 8.1 High

Published by the GitHub Advisory Database at 17 Dec 2021, 20:42 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
ru.yandex.clickhouse:clickhouse-jdbc-bridgeMaven<2.0.72.0.7
Identifiers
GHSA-3w6p-8f82-gw8r
Weakness (CWE)
CWE-502
Published
17 Dec 2021
Updated
3 Dec 2024

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Versions of ru.yandex.clickhouse:clickhouse-jdbc-bridge before 2.0.7 are affected. The bridge's bundled log4j 1.2.17 can deserialize untrusted data through JMSAppender, but only if the log4j configuration was changed to use JMSAppender with an insecure JMS broker. A remote attacker in that setup could execute code on the server. Upgrade to 2.0.7, which removed the log4j dependency; alternatively, do not configure JMSAppender with an insecure JMS broker.

Written 8 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.1 High 3.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H GitHub Advisory Database
  • CISA KEV Not listed.
  • EPSS No score.

Timeline

  1. 31 Oct 2026, 15:12 UTC First seen by agentprime
  2. 31 Oct 2026, 15:12 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.