dbcve.org
PulsarApplication · Apache

CVE-2022-33682

MEDIUM · 5.9 CVSS v3.1 Published 2022-09-23
Fix available
A fix is available. Upgrade to 2.7.5 / 2.8.4 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Apache Pulsar client components (Broker Java Client, Broker Java Admin Client, WebSocket Proxy Java Client, and Proxy Admin Client) cannot enable TLS hostname verification, allowing MITM attackers to intercept intra-cluster and geo-replication connections by presenting a valid certificate for an unrelated host. This affects both pulsar+ssl and HTTPS protocols.

MitigationEnable TLS hostname verification in the affected Pulsar client components to ensure clients verify the server's certificate matches the intended hostname. If hostname verification cannot be enabled via configuration, upgrade to a patched version.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
PulsarApplication
Affected:< 2.7.5>= 2.8.0, < 2.8.4>= 2.9.0, < 2.9.3= 2.10.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Pulsar version
    Run 'pulsar-admin broker-version' or check the version of pulsar-client packages installed via package manager
    Affected if Version is < 2.7.5, >= 2.8.0 and < 2.8.4, >= 2.9.0 and < 2.9.3, or exactly 2.10.0
  2. Confirm TLS/SSL usage
    Review client configuration files for 'tlsEnabled=true', 'sslTrustCertsFilePath' settings, or connection URLs using 'pulsar+ssl://' or 'https://'
    Affected if TLS or HTTPS is enabled for client connections
  3. Check hostname verification configuration
    Inspect client config for 'tlsHostnameVerificationEnabled=true' or 'hostnameVerification=true' in broker.conf, web.conf, or client connection settings
    Affected if Hostname verification is disabled (false) or not explicitly set to true (defaults to false in affected versions)

You are affected if you run an affected Pulsar version AND use TLS/SSL client connections with hostname verification disabled or not explicitly enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.7.5 / 2.8.4 / 2.9.3 or later
Fixed in 2.7.52.8.42.9.3
Interim mitigation

Enable TLS hostname verification in the affected Pulsar client components to ensure clients verify the server's certificate matches the intended hostname. If hostname verification cannot be enabled via configuration, upgrade to a patched version.

Recommended fix High confidence

Upgrade to Pulsar 2.7.5+, 2.8.4+, 2.9.3+, or 2.10.1+ (choose the latest stable release in your preferred branch)

  1. 1. Identify all Pulsar Broker, Proxy, and WebSocket Proxy instances running affected versions in your environment
  2. 2. Upgrade Pulsar Broker/Proxy instances from 2.7.0-2.7.4 to version 2.7.5 or later
  3. 3. Upgrade Pulsar Broker/Proxy instances from 2.8.0-2.8.3 to version 2.8.4 or later
  4. 4. Upgrade Pulsar Broker/Proxy instances from 2.9.0-2.9.2 to version 2.9.3 or later
  5. 5. Upgrade Pulsar Broker/Proxy instances at version 2.10.0 to version 2.10.1 or later
  6. 6. After upgrade, explicitly configure TLS hostname verification in client connections using the appropriate configuration options (e.g., 'tlsHostnameVerificationEnable=true' in broker.conf/proxy.conf)
  7. 7. Verify that hostname verification is functioning by testing TLS connections with invalid hostnames
Caveat Major version upgrades may introduce breaking changes; review release notes for your target version for any configuration or API changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Pulsar Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-33682 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-33682 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data