CVE-2022-33682

Published on: Not Yet Published

Last Modified on: 09/27/2022 01:23:00 PM UTC

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

Certain versions of Pulsar from Apache contain the following vulnerability:

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.

  • CVE-2022-33682 has been assigned by URL Logo [email protected] to track the vulnerability - currently rated as MEDIUM severity.
  • Affected Vendor/Software: URL Logo Apache Software Foundation - Apache Pulsar version <= 2.7.4
  • Affected Vendor/Software: URL Logo Apache Software Foundation - Apache Pulsar version <= 2.8.3
  • Affected Vendor/Software: URL Logo Apache Software Foundation - Apache Pulsar version <= 2.9.2
  • Affected Vendor/Software: URL Logo Apache Software Foundation - Apache Pulsar version = 2.10.0
  • Affected Vendor/Software: URL Logo Apache Software Foundation - Apache Pulsar version <= 2.6.4
Vulnerability Patch/Work Around
  • Any users running affected versions of the Pulsar Broker, Pulsar Proxy, or Pulsar WebSocket Proxy should rotate static authentication data vulnerable to man in the middle attacks used by these applications, including tokens and passwords. To enable hostname verification, update the following configuration files. In the Broker configuration (broker.conf, by default) and in the WebSocket Proxy configuration (websocket.conf, by default), set: brokerClient_tlsHostnameVerificationEnable=true In Pulsar Helm chart deployments, the Broker and WebSocket Proxy setting name should be prefixed with "PULSAR_PREFIX_". In the Proxy configuration (proxy.conf, by default), set: tlsHostnameVerificationEnabled=true 2.7 users should upgrade Pulsar Brokers, Proxies, and WebSocket Proxies to 2.7.5, rotate vulnerable authentication data, including tokens and passwords, and apply the above configuration. 2.8 users should upgrade Pulsar Brokers, Proxies, and WebSocket Proxies to 2.8.4, rotate vulnerable authentication data, including tokens and passwords, and apply the above configuration. 2.9 users should upgrade Pulsar Brokers, Proxies, and WebSocket Proxies to 2.9.3, rotate vulnerable authentication data, including tokens and passwords, and apply the above configuration. 2.10 users should upgrade Pulsar Brokers, Proxies, and WebSocket Proxies to 2.10.1, rotate vulnerable authentication data, including tokens and passwords, and apply the above configuration. Any users running Pulsar Brokers, Proxies, and WebSocket Proxies for 2.6.4 and earlier should upgrade to one of the above patched versions, rotate vulnerable authentication data, including tokens and passwords, and apply the above configuration.

CVSS3 Score: 5.9 - MEDIUM

Attack
Vector
Attack
Complexity
Privileges
Required
User
Interaction
NETWORK HIGH NONE NONE
Scope Confidentiality
Impact
Integrity
Impact
Availability
Impact
UNCHANGED HIGH NONE NONE

CVE References

Description Tags Link
No Description Provided lists.apache.org
text/html
URL Logo MISC lists.apache.org/thread/l0ynfl161qghwfcgbbl8ld9hzbl9t3yx

Known Affected Configurations (CPE V2.3)

Type Vendor Product Version Update Edition Language
ApplicationApachePulsarAllAllAllAll
ApplicationApachePulsar2.10.0-AllAll
  • cpe:2.3:a:apache:pulsar:*:*:*:*:*:*:*:*:
  • cpe:2.3:a:apache:pulsar:2.10.0:-:*:*:*:*:*:*:

Discovery Credit

This issue was discovered by Michael Marshall of DataStax.

Social Mentions

Source Title Posted (UTC)
Twitter Icon @CVEreport CVE-2022-33682 : TLS hostname verification cannot be enabled in the Pulsar Broker's Java Client, the Pulsar Broker'… twitter.com/i/web/status/1… 2022-09-23 09:27:14
Reddit Logo Icon /r/netcve CVE-2022-33682 2022-09-23 10:38:14
© CVE.report 2022 Twitter Nitter Twitter Viewer |

Use of this information constitutes acceptance for use in an AS IS condition. There are NO warranties, implied or otherwise, with regard to this information or its use. Any use of this information is at the user's risk. It is the responsibility of user to evaluate the accuracy, completeness or usefulness of any information, opinion, advice or other content. EACH USER WILL BE SOLELY RESPONSIBLE FOR ANY consequences of his or her direct or indirect use of this web site. ALL WARRANTIES OF ANY KIND ARE EXPRESSLY DISCLAIMED. This site will NOT BE LIABLE FOR ANY DIRECT, INDIRECT or any other kind of loss.

CVE, CWE, and OVAL are registred trademarks of The MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. This site includes MITRE data granted under the following license.

CVE.report and Source URL Uptime Status status.cve.report