CVE-2022-33684

HIGHNVD 8.18.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This high-severity CVE scores 8.1 under NVD CVSS v3. EPSS exploit probability: 0.8% (55th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated this week
8.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.8%CVSS: 8.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

The Apache Pulsar C++ Client does not verify peer TLS certificates when making HTTPS calls for the OAuth2.0 Client Credential Flow, even when tlsAllowInsecureConnection is disabled via configuration. This vulnerability allows an attacker to perform a man in the middle attack and intercept and/or modify the GET request that is sent to the ClientCredentialFlow 'issuer url'. The intercepted credentials can be used to acquire authentication data from the OAuth2.0 server to then authenticate with an Apache Pulsar cluster. An attacker can only take advantage of this vulnerability by taking control of a machine 'between' the client and the server. The attacker must then actively manipulate traffic to perform the attack. The Apache Pulsar Python Client wraps the C++ client, so it is also vulnerable in the same way. This issue affects Apache Pulsar C++ Client and Python Client versions 2.7.0 to 2.7.4; 2.8.0 to 2.8.3; 2.9.0 to 2.9.2; 2.10.0 to 2.10.1; 2.6.4 and earlier. Any users running affected versions of the C++ Client or the Python Client should rotate vulnerable OAuth2.0 credentials, including client_id and client_secret. 2.7 C++ and Python Client users should upgrade to 2.7.5 and rotate vulnerable OAuth2.0 credentials. 2.8 C++ and Python Client users should upgrade to 2.8.4 and rotate vulnerable OAuth2.0 credentials. 2.9 C++ and Python Client users should upgrade to 2.9.3 and rotate vulnerable OAuth2.0 credentials. 2.10 C++ and Python Client users should upgrade to 2.10.2 and rotate vulnerable OAuth2.0 credentials. 3.0 C++ users are unaffected and 3.0 Python Client users will be unaffected when it is released. Any users running the C++ and Python Client for 2.6 or less should upgrade to one of the above patched versions.

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
37
EG Risk 37/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity81% × 45%
Impact severity (EG Severity): CVSS 8.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.8% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.8%
EPSS %ILE
55th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.1): severity, escalated by confirmed exploitation. This CVE's 8.1 is its impact severity (EG Severity), not escalated.

EG Severity
8.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.8% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-20). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 4, 2022

Last Modified

May 2, 2025

Advisory Details (2)

Auto-updated Sep 17, 2026
Patch available.
Web page
https://lists.apache.org/thread/ky1ssskvkj00y36k7nys9b5gm5jjrzwv
Web page

huntr - The world's first bug bounty platform for AI/ML

https://huntr.dev/bounties/df89b724-3201-47aa-b8cd-282e112a566f

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
pulsar-client1.18.dev1 ... 2.9.2 (43 versions)
  • every version up to 2.7.5: fixed in 2.7.5
  • 2.8.0 up to 2.8.4: fixed in 2.8.4
  • 2.9.0 up to 2.9.3: fixed in 2.9.3
  • 2.10.0 up to 2.10.2: fixed in 2.10.2
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 33× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 92 of 196 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 8 repeat rows among the latest 100 are merged into the row they repeat. The 104 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-21 16:29 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  2. 2026-10-21 06:59 UTCEG score recompute
  3. 2026-10-20 16:29 UTCEPSS rescoreEPSS 0.8% · 55th percentile
  4. 2026-10-19 16:28 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  5. 2026-10-18 16:28 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  6. 2026-10-18 08:33 UTCEG score recompute
  7. 2026-10-17 16:29 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  8. 2026-10-16 16:35 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  9. 2026-10-15 16:28 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  10. 2026-10-15 12:24 UTCOSV refresh
  11. 2026-10-14 16:29 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  12. 2026-10-13 16:29 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  13. 2026-10-12 18:52 UTCEG score recompute
  14. 2026-10-12 16:30 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  15. 2026-10-11 23:17 UTCEG score recompute
  16. 2026-10-11 13:44 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  17. 2026-10-10 19:56 UTCEPSS rescoreEPSS 0.8% · 54th percentile
  18. 2026-10-09 20:04 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  19. 2026-10-08 16:40 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  20. 2026-10-07 23:45 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  21. 2026-10-06 15:14 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  22. 2026-10-05 17:40 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  23. 2026-10-03 14:23 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  24. 2026-10-02 16:23 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  25. 2026-10-01 19:47 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
Show 67 more
  1. 2026-09-30 15:57 UTCEG score recompute
  2. 2026-09-30 15:00 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  3. 2026-09-29 15:16 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  4. 2026-09-27 13:42 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  5. 2026-09-26 00:22 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  6. 2026-09-24 14:00 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  7. 2026-09-24 06:48 UTCOSV refresh
  8. 2026-09-22 14:45 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  9. 2026-09-20 20:13 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  10. 2026-09-19 15:38 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  11. 2026-09-17 19:24 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  12. 2026-09-16 14:05 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  13. 2026-09-15 03:07 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  14. 2026-09-12 14:57 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  15. 2026-09-11 14:50 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  16. 2026-09-11 09:33 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  17. 2026-09-08 21:57 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  18. 2026-09-07 15:58 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  19. 2026-09-06 13:45 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  20. 2026-09-05 15:25 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  21. 2026-09-04 23:59 UTCOSV refresh
  22. 2026-09-04 13:57 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  23. 2026-09-04 05:04 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  24. 2026-09-02 14:09 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  25. 2026-09-01 13:51 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  26. 2026-08-30 19:14 UTCEPSS rescoreEPSS 0.7% · 51st percentile
  27. 2026-08-30 01:19 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  28. 2026-08-28 21:38 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  29. 2026-08-27 14:22 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  30. 2026-08-26 14:43 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  31. 2026-08-25 13:46 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  32. 2026-08-24 14:13 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  33. 2026-08-23 00:17 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  34. 2026-08-21 23:46 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  35. 2026-08-20 22:52 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  36. 2026-08-19 17:01 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  37. 2026-08-18 13:45 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  38. 2026-08-18 10:51 UTCOSV refresh
  39. 2026-08-17 13:44 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  40. 2026-08-16 14:53 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  41. 2026-08-16 02:11 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  42. 2026-08-15 01:27 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  43. 2026-08-13 21:58 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  44. 2026-08-12 13:48 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  45. 2026-08-11 13:39 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  46. 2026-08-10 14:08 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  47. 2026-08-09 13:44 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  48. 2026-08-08 16:34 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  49. 2026-08-07 16:24 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  50. 2026-08-06 13:44 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  51. 2026-08-05 19:15 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  52. 2026-08-04 15:07 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  53. 2026-08-04 10:35 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  54. 2026-08-03 06:27 UTCOSV refresh
  55. 2026-08-02 02:24 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  56. 2026-08-01 04:13 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  57. 2026-07-30 16:25 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  58. 2026-07-30 01:28 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  59. 2026-07-28 15:33 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  60. 2026-07-26 14:52 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  61. 2026-07-25 14:15 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  62. 2026-07-24 14:15 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  63. 2026-07-23 14:16 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  64. 2026-07-23 02:11 UTCEG score recompute
  65. 2026-07-22 22:59 UTCEG score recompute
  66. 2026-07-22 14:06 UTCEPSS rescoreEPSS 0.7% · 49th percentile
  67. 2026-07-21 15:23 UTCEPSS rescoreEPSS 0.7% · 49th percentile

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2022-33684?
CVE-2022-33684 is a high-severity vulnerability; its CVE record was published on November 4, 2022. The Apache Pulsar C++ Client does not verify peer TLS certificates when making HTTPS calls for the OAuth2.0 Client Credential Flow, even when tlsAllowInsecureConnection is disabled via configuration. This vulnerability allows an attacker to perform a man in the middle attack and intercept and/or…
When was the CVE record for CVE-2022-33684 published?
The CVE record for CVE-2022-33684 was published on November 4, 2022. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of May 2, 2025; the record at its source may have been updated since.
Is CVE-2022-33684 actively exploited?
CVE-2022-33684 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.8% probability of exploitation in the next 30 days (55th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-33684?
CVE-2022-33684 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2022-33684?
A fix for CVE-2022-33684 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-33684

Explore →

Is Your Infrastructure Affected by CVE-2022-33684?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs