← Back
CVE-2022-33684
Vulnerability in pulsar-client (CVE-2022-33684)
Summary
vulnerability in pulsar-client (CVE-2022-33684). Successful exploitation can lead to full system takeover. Exploitable via ``tlsAllowInsecureConnection``. Mitigation: upgrade to `2.10.2` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2022-33684** has been found in pulsar-client.
Attackers can target a specific entry point like ``tlsAllowInsecureConnection`` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: ?/10.
What to do: upgrade pulsar-client to **2.10.2** or later.
If unsure, ask your IT team or search "pulsar-client CVE-2022-33684" on the vendor's site.
CVE-2022-33684 (pulsar-client) — CWE-295 /
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `tlsAllowInsecureConnection` / `ClientCredentialFlow` / `client_id` / `client_secret`
Patched: `2.10.2` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-295) exists in pulsar-client. Attackers reach the vulnerable code path via ``tlsAllowInsecureConnection`` without authentication.
📍 Affected scope
pulsar-client — . Attack surface: `tlsAllowInsecureConnection` / `ClientCredentialFlow` / `client_id` / `client_secret`.
🔥 Severity
Severity: ?. Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **2.10.2**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'pulsar-client' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'pulsar-client' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `pulsar-client` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade pulsar-client to 2.10.2ステージング環境で 2.10.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
pulsar-client
[{"type":"ECOSYSTEM","events":[{"introduced":"2.10.0"},{"fixed":"2.10.2"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2022-33684
- advisory https://github.com/advisories/GHSA-5r3h-c3r7-9w4h
- package https://github.com/apache/pulsar-client-cpp
- package https://pypi.org/project/pulsar-client
- web https://github.com/apache/pulsar/pull/16064
- web https://huntr.dev/bounties/df89b724-3201-47aa-b8cd-282e112a566f
- web https://lists.apache.org/thread/ky1ssskvkj00y36k7nys9b5gm5jjrzwv