Skip to content
Noroxi
CVE-2022-33682· NVD / CVE Program· CNA apache

Disabled Hostname Verification makes Brokers, Proxies vulnerable to MITM attack

TLS hostname verification cannot be enabled in the Pulsar Broker's Java Client, the Pulsar Broker's Java Admin Client, the Pulsar WebSocket Proxy's Java Client, and the Pulsar Proxy's Admin Client leaving intra-cluster connections and geo-replication connections vulnerable to man in the middle attacks, which could leak credentials, configuration data, message data, and any other data sent by these clients. The vulnerability is for both the pulsar+ssl protocol and HTTPS. 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 by providing the client with a cryptographically valid certificate for an unrelated host. This issue affects Apache Pulsar Broker, Proxy, and WebSocket 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.

MediumCVSS 5.9 · v3.1—No exploit Fix available
Published
Sep 23, 2022
Updated
Jun 17, 2026
EPSS
0.7% · 52th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

23

Monitor

Low priority for now.

CVSS
23 / 40 · 5.9 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.7%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Affected systems

VendorProduct
apachepulsar

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • apache pulsarbefore 2.7.5
  • apache pulsar2.8.0 and later · before 2.8.4
  • apache pulsar2.9.0 and later · before 2.9.3
  • apache pulsar2.10.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (apache). Independent of NVD's CPE analysis and usually ahead of it.

  • Apache Software Foundation Apache Pulsar

    • 2.10.0affected
    • 2.7 and later · up to and including 2.7.4affected
    • 2.8 and later · up to and including 2.8.3affected
    • 2.9 and later · up to and including 2.9.2affected
    • 2.6 and earlier and later · up to and including 2.6.4affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Mavenorg.apache.pulsar:pulsar-brokerfrom 2.10.0 · before 2.10.12.10.1
Mavenorg.apache.pulsar:pulsar-brokerfrom 2.8.0 · before 2.8.42.8.4
Mavenorg.apache.pulsar:pulsar-brokerfrom 2.9.0 · before 2.9.32.9.3
Mavenorg.apache.pulsar:pulsar-brokerbefore 2.7.52.7.5
Mavenorg.apache.pulsar:pulsar-proxyfrom 2.10.0 · before 2.10.12.10.1
Mavenorg.apache.pulsar:pulsar-proxyfrom 2.8.0 · before 2.8.42.8.4
Mavenorg.apache.pulsar:pulsar-proxyfrom 2.9.0 · before 2.9.32.9.3
Mavenorg.apache.pulsar:pulsar-proxybefore 2.7.52.7.5

Same product

apache: all records

Other highest-scoring records for the same primary product.

  • CVE-2024-27317Apache Pulsar: Pulsar Functions Worker's Archive Extraction Vulnerability Allows Unauthorized File Modification
    56Plan
  • CVE-2021-22160Authentication with JWT allows use of “none”-algorithm
    55Plan
  • CVE-2024-27135Apache Pulsar: Improper Input Validation in Pulsar Function Worker allows Remote Code Execution
    41Plan
  • CVE-2024-27894Apache Pulsar: Pulsar Functions Worker Allows Unauthorized File Access and Unauthorized HTTP/HTTPS Proxying
    36Monitor
  • CVE-2023-30429Apache Pulsar: Incorrect Authorization for Function Worker when using mTLS Authentication through Pulsar Proxy
    35Monitor
  • CVE-2022-34321Apache Pulsar: Improper Authentication for Pulsar Proxy Statistics Endpoint
    33Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Maven:org.apache.pulsar:pulsar-broker2.10.1Package registry (OSV)
Maven:org.apache.pulsar:pulsar-broker2.7.5Package registry (OSV)
Maven:org.apache.pulsar:pulsar-broker2.8.4Package registry (OSV)
Maven:org.apache.pulsar:pulsar-broker2.9.3Package registry (OSV)
Maven:org.apache.pulsar:pulsar-proxy2.10.1Package registry (OSV)
Maven:org.apache.pulsar:pulsar-proxy2.7.5Package registry (OSV)
Maven:org.apache.pulsar:pulsar-proxy2.8.4Package registry (OSV)
Maven:org.apache.pulsar:pulsar-proxy2.9.3Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
high · data can be read
Integrity
none
Availability
none
Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
None
Availability impact
None

Weakness class (CWE)

CWE-295 · Improper Certificate Validation

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

nvd-primary

Root cause

A certificate validation error is silently swallowed instead of terminating the connection. Often, code added for a test environment makes its way into production.

The bug in code

The whole CWE-295 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

kotlin
override fun checkServerTrusted(chain: Array<X509Certificate>, type: String) {  // Left empty for the test environment}

Fixed

kotlin
val client = OkHttpClient.Builder()  .certificatePinner(    CertificatePinner.Builder()      .add("api.sirius.example", "sha256/…")      .build()  ).build()

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records