Read the docs
TI-2022-14799 Aliases CVE-2022-33681GHSA-c5fp-x2h5-vjv7

Improper Hostname Verification in Java Client and Proxy can expose authentication data via MITM

Priority LOW 28CWE-295Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
High
Impact type
Spoofing
Confidentiality · integrity · availability
High · None · None
Fix status
Partial Red Hat: 1 fixed, 3 without a fix

Attack profile from CVSS 3.1 · CISA ADP. Fix status from CNA, GitHub and Red Hat. Impact type from CWE-295.

Summary

Delayed TLS hostname verification in the Pulsar Java Client and the Pulsar Proxy make each client vulnerable to a man in the middle attack. Connections from the Pulsar Java Client to the Pulsar Broker/Proxy and connections from the Pulsar Proxy to the Pulsar Broker are vulnerable. Authentication data is sent before verifying the server’s TLS certificate matches the hostname, which means authentication data could be exposed to an attacker. 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. Because the client sends authentication data before performing hostname verification, an attacker could gain access to the client’s authentication data. The client eventually closes the connection when it verifies the hostname and identifies the targeted hostname does not match a hostname on the certificate. Because the client eventually closes the connection, the value of the intercepted authentication data depends on the authentication method used by the client. Token based authentication and username/password authentication methods are vulnerable because the authentication data can be used to impersonate the client in a separate session. This issue affects Apache Pulsar Java 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; 2.6.4 and earlier.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00697 53rd percentileScored 2026-11-07
Fix Partial org.apache.pulsar:pulsar-client (Maven): 2.7.5, 2.8.4, 2.9.3 +1Red Hat: 1 advisoryRed Hat: 1 fixed, 3 without a fix

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
ApacheApache Pulsar2.10.0; 2.7 – 2.7.4; 2.8 – 2.8.3; 2.9 – 2.9.2; 2.6 and earlier – 2.6.4—No fix listedCNA
—org.apache.pulsar:pulsar-client (Maven)before 2.7.52.7.5Patch availableGHSA-c5fp-x2h5-vjv7
—org.apache.pulsar:pulsar-client (Maven)2.8.0 to before 2.8.42.8.4Patch availableGHSA-c5fp-x2h5-vjv7
—org.apache.pulsar:pulsar-client (Maven)2.9.0 to before 2.9.32.9.3Patch availableGHSA-c5fp-x2h5-vjv7
—org.apache.pulsar:pulsar-client (Maven)2.10.0 to before 2.10.12.10.1Patch availableGHSA-c5fp-x2h5-vjv7
  • Apache Pulsar VendorApache Affected 2.10.0; 2.7 – 2.7.4; 2.8 – 2.8.3; 2.9 – 2.9.2; 2.6 and earlier – 2.6.4 Fixed in — No fix listed CNA
  • org.apache.pulsar:pulsar-client (Maven) Vendor— Affected before 2.7.5 Fixed in 2.7.5 Patch available GHSA-c5fp-x2h5-vjv7
  • org.apache.pulsar:pulsar-client (Maven) Vendor— Affected 2.8.0 to before 2.8.4 Fixed in 2.8.4 Patch available GHSA-c5fp-x2h5-vjv7
  • org.apache.pulsar:pulsar-client (Maven) Vendor— Affected 2.9.0 to before 2.9.3 Fixed in 2.9.3 Patch available GHSA-c5fp-x2h5-vjv7
  • org.apache.pulsar:pulsar-client (Maven) Vendor— Affected 2.10.0 to before 2.10.1 Fixed in 2.10.1 Patch available GHSA-c5fp-x2h5-vjv7

CPE configurations NVD · 2

CPEVersionsRoleVendor
cpe:2.3:a:apache:pulsar:*:*:*:*:*:*:*:*before 2.7.5; 2.8.0 to before 2.8.4; 2.9.0 to before 2.9.3VulnerableApache
cpe:2.3:a:apache:pulsar:2.10.0:-:*:*:*:*:*:*2.10.0VulnerableApache
  • cpe:2.3:a:apache:pulsar:*:*:*:*:*:*:*:* Versions before 2.7.5; 2.8.0 to before 2.8.4; 2.9.0 to before 2.9.3 Vulnerable ·Apache
  • cpe:2.3:a:apache:pulsar:2.10.0:-:*:*:*:*:*:* Versions 2.10.0 Vulnerable ·Apache

Remediation

  • Fix · GHSA-c5fp-x2h5-vjv7 org.apache.pulsar:pulsar-client (Maven) Fixed in 2.7.5 Advisory →
  • Fix · GHSA-c5fp-x2h5-vjv7 org.apache.pulsar:pulsar-client (Maven) Fixed in 2.8.4 Advisory →
  • Fix · GHSA-c5fp-x2h5-vjv7 org.apache.pulsar:pulsar-client (Maven) Fixed in 2.9.3 Advisory →
  • Fix · GHSA-c5fp-x2h5-vjv7 org.apache.pulsar:pulsar-client (Maven) Fixed in 2.10.1 Advisory →

Red Hat 1 advisory

  • RHSA-2023:2100 Released 2023-05-03 · Red Hat rating Important
    Red Hat Integration Camel for Spring Boot 3.20.1 security update
    • RHINT Camel-Springboot 3.20.1

Vendor assessments

Red Hat

Red Hat rating: Moderate. Red Hat's page for this CVE →

ProductStatusPlan or fix
Red Hat Fuse 7AffectedNo fix planned: Will not fix
Red Hat Integration Camel K 1AffectedNo fix planned: Will not fix
Red Hat Integration Camel Quarkus 1AffectedNo fix planned: Will not fix
RHINT Camel-Springboot 3.20.1Fixed RHSA-2023:2100

Timeline

  1. 2026-10-02 Threatist record created from CVE-2022-33681
  2. 2026-10-03 Alias added: GHSA-c5fp-x2h5-vjv7

References

Advisory 2

Other 1

  • TI-2024-18155 Apache Pulsar: Pulsar Functions Worker's Archive Extraction Vulnerability Allows Unauthorized File Modification CVSS 3.1CRITICAL 9.9
  • TI-2021-05150 Authentication with JWT allows use of “none”-algorithm CVSS 3.1CRITICAL 9.8
  • TI-2024-17990 Apache Pulsar: Improper Input Validation in Pulsar Function Worker allows Remote Code Execution CVSS 3.1CRITICAL 9.9
  • TI-2023-14272 Apache Pulsar: Incorrect Authorization for Function Worker when using mTLS Authentication through Pulsar Proxy CVSS 3.1CRITICAL 9.6
  • TI-2022-15232 Apache Pulsar: Improper Authentication for Pulsar Proxy Statistics Endpoint CVSS 3.1HIGH 8.2
  • TI-2024-18500 Apache Pulsar: Pulsar Functions Worker Allows Unauthorized File Access and Unauthorized HTTP/HTTPS Proxying CVSS 3.1HIGH 8.8
See all 19 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences