{"answers":{"affected":"2 open source packages ship an affected version, including ru.yandex.clickhouse:clickhouse-jdbc-bridge.","exploited":"There is no known exploitation of GHSA-3w6p-8f82-gw8r in the wild and no public exploit code.","fix":"Upgrade ru.yandex.clickhouse:clickhouse-jdbc-bridge to 2.0.7 or later.","what":"GHSA-3w6p-8f82-gw8r is an unsafe deserialization vulnerability in ru.yandex.clickhouse:clickhouse-jdbc-bridge, published on 17 Dec 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for GHSA-3w6p-8f82-gw8r and fix it if it is affected.\n\nWhat it is: GHSA-3w6p-8f82-gw8r is an unsafe deserialization vulnerability in ru.yandex.clickhouse:clickhouse-jdbc-bridge, published on 17 Dec 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of GHSA-3w6p-8f82-gw8r in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- ru.yandex.clickhouse:clickhouse-jdbc-bridge (Maven): affected all versions; fixed in 2.0.7\n- ru.yandex.clickhouse:clickhouse-jdbc-bridge (Maven): affected all versions; fixed in 2.0.7\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/GHSA-3w6p-8f82-gw8r/ (Markdown: https://insights.sbomify.com/GHSA-3w6p-8f82-gw8r/index.md)","id":"GHSA-3w6p-8f82-gw8r","markdown":"https://insights.sbomify.com/GHSA-3w6p-8f82-gw8r/index.md","name":"GHSA-3w6p-8f82-gw8r","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"ClickHouse JDBC Bridge","requires_auth":"none","summary":"Remote attackers can execute code if the ClickHouse JDBC Bridge uses a non-default log4j configuration with JMSAppender and an insecure broker.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"### Impact\n\nClickHouse 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.\n\n### Patches\n\nThe 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`.\n\n### Workarounds\n\n1. Do NOT change log4j configuration to use JMSAppender along with insecure JMS broker\n2. Alternatively, you can issue below command to remove `JMSAppender.class`:\n\n```(bash)\n# install zip command if you don't have\napt-get update \u0026\u0026 apt-get install -y zip\n# remove the class\nzip -d clickhouse-jdbc-bridge*.jar ru/yandex/clickhouse/jdbcbridge/internal/log4j/net/JMSAppender.class\n```\n\n### References\n\nPlease refer to [CVE-2021-4104](https://access.redhat.com/security/cve/CVE-2021-4104) to read more.\n\n### For more information\n\nIf you have any questions or comments about this advisory, please feel free to open an issue in the repository.","ecosystems":["Maven"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"Using JMSAppender in log4j configuration may lead to deserialization of untrusted data","id":"GHSA-3w6p-8f82-gw8r","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"Maven","product":null,"products":[],"type":"deserialization","year":"2021"},"n_packages":2,"n_references":null,"packages":[{"ecosystem":"Maven","fixed":["2.0.7"],"introduced":["0"],"last_affected":[],"package":"ru.yandex.clickhouse:clickhouse-jdbc-bridge","purl":null,"source":"GHSA-3w6p-8f82-gw8r"},{"ecosystem":"Maven","fixed":["2.0.7"],"introduced":["0"],"last_affected":[],"package":"ru.yandex.clickhouse:clickhouse-jdbc-bridge","purl":"pkg:maven/ru.yandex.clickhouse/clickhouse-jdbc-bridge","source":"GHSA-3w6p-8f82-gw8r"}],"products":null,"published":"2021-12-17","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"Remote attackers can execute code if the ClickHouse JDBC Bridge uses a non-default log4j configuration with JMSAppender and an insecure broker.","url":"https://insights.sbomify.com/GHSA-3w6p-8f82-gw8r/"}