CVE-2022-33683

MEDIUMNVD 5.95.9—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.9 under NVD CVSS v3. EPSS exploit probability: 0.7% (50th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
5.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 5.9Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Apache Pulsar Brokers and Proxies create an internal Pulsar Admin Client that does not verify peer TLS certificates, even when tlsAllowInsecureConnection is disabled via configuration. The Pulsar Admin Client's intra-cluster and geo-replication HTTPS connections are vulnerable to man in the middle attacks, which could leak authentication data, configuration data, and any other data sent by these clients. 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. This issue affects Apache Pulsar Broker and Proxy 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; 2.6.4 and earlier.

CVSS v3
5.9
EG Score
5.9MEDIUMmedium confidence
EG Risk
27
EG Risk 27/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity59% × 45%
Exploitation1% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.7%
EPSS %ILE
51st
KEV
Not listed

CISA SSVCTrack at every mission impact level.

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 23, 2022

Last Modified

May 22, 2025

References (2)

Affected Packages

(2 across 1 ecosystem)
Maven(2)
PackageVulnerable rangeFix by version rangeDependents
org.apache.pulsar:pulsar-broker2.10.0
  • 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.1: fixed in 2.10.1
—
org.apache.pulsar:pulsar-proxy2.10.0
  • 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.1: fixed in 2.10.1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 27× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 189 total refreshes for this CVE.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2022-33683?
CVE-2022-33683 is a medium vulnerability published on September 23, 2022. Apache Pulsar Brokers and Proxies create an internal Pulsar Admin Client that does not verify peer TLS certificates, even when tlsAllowInsecureConnection is disabled via configuration. The Pulsar Admin Client's intra-cluster and geo-replication HTTPS connections are vulnerable to man in the middle…
When was CVE-2022-33683 disclosed?
CVE-2022-33683 was first published on September 23, 2022, with the most recent update on May 22, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-33683 actively exploited?
CVE-2022-33683 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (51st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-33683?
CVE-2022-33683 has a CVSS v3 base score of 5.9 (NVD).
How do I remediate CVE-2022-33683?
A fix for CVE-2022-33683 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-33683

Explore →

Is Your Infrastructure Affected by CVE-2022-33683?

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

Book a Demo →Browse All CVEs