Security readout for executives and security teams
Plain-English summary
Apache Pulsar components could fail to verify that a TLS certificate matches the intended hostname. If an attacker controls a network point between Pulsar components, they may intercept confidential traffic such as credentials, configuration, or message data.
Executive priority
Treat as a confidentiality risk for Pulsar environments, not a broad internet worm risk. Prioritize remediation where Pulsar carries sensitive messages, credentials, or configuration across networks that attackers could influence.
Technical view
CVE-2022-33682 is a CWE-295 hostname-verification issue affecting Pulsar Broker, Proxy, and WebSocket Proxy Java client/admin connections over pulsar+ssl and HTTPS. The source states hostname verification could not be enabled for several internal clients, enabling MITM confidentiality compromise under high-complexity network positioning conditions.
Likely exposure
Exposure is most likely in Apache Pulsar deployments using affected Broker, Proxy, or WebSocket Proxy versions, especially intra-cluster or geo-replication connections using TLS. Affected ranges include 2.6.4 and earlier, 2.7.0-2.7.4, 2.8.0-2.8.3, 2.9.0-2.9.2, and 2.10.0.
Exploitation context
The source bundle does not show KEV listing or active exploitation. Exploitation requires attacker control of a machine or network position between client and server, plus active traffic manipulation using a cryptographically valid certificate for an unrelated host.
Researcher notes
The key constraint is network position. Validation should focus on affected component versions and TLS client paths named in the advisory. The provided sources do not establish integrity or availability impact, active exploitation, or a specific patch version.
Mitigation direction
- Inventory Pulsar Broker, Proxy, and WebSocket Proxy versions.
- Check Apache advisory guidance for fixed versions and upgrade direction.
- Prioritize TLS protection for intra-cluster and geo-replication paths.
- Limit who can control intermediate network infrastructure.
- Review credential exposure if suspicious MITM conditions existed.
Validation and detection
- Confirm whether deployed Pulsar versions fall in affected ranges.
- Map Pulsar TLS connections using pulsar+ssl and HTTPS.
- Identify intra-cluster and geo-replication paths crossing untrusted networks.
- Review vendor guidance for hostname verification behavior after remediation.
- Check monitoring for unexpected TLS endpoints or certificate anomalies.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-295: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2022-33682 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.9 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N2.23.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.9MediumVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://lists.apache.org/thread/l0ynfl161qghwfcgbbl8ld9hzbl9t3yxCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Certificate Validation
Improper Certificate Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.