CVE-2022-33684

The Apache Pulsar C++ Client does not verify peer TLS certificates when making HTTPS calls for the OAuth2.0 Client Credential Flow, even when tlsAllowInsecureConnection is disabled via configuration. This vulnerability allows an attacker to perform a man in the middle attack and intercept and/or modify the GET request that is sent to the ClientCredentialFlow 'issuer url'. The intercepted credentials can be used to acquire authentication data from the OAuth2.0 server to then authenticate with an Apache Pulsar cluster. 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. The Apache Pulsar Python Client wraps the C++ client, so it is also vulnerable in the same way. This issue affects Apache Pulsar C++ Client and Python 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 to 2.10.1; 2.6.4 and earlier. Any users running affected versions of the C++ Client or the Python Client should rotate vulnerable OAuth2.0 credentials, including client_id and client_secret. 2.7 C++ and Python Client users should upgrade to 2.7.5 and rotate vulnerable OAuth2.0 credentials. 2.8 C++ and Python Client users should upgrade to 2.8.4 and rotate vulnerable OAuth2.0 credentials. 2.9 C++ and Python Client users should upgrade to 2.9.3 and rotate vulnerable OAuth2.0 credentials. 2.10 C++ and Python Client users should upgrade to 2.10.2 and rotate vulnerable OAuth2.0 credentials. 3.0 C++ users are unaffected and 3.0 Python Client users will be unaffected when it is released. Any users running the C++ and Python Client for 2.6 or less should upgrade to one of the above patched versions.

• CWE-295
• CWE-295
• CWE-295

• https://huntr.dev/bounties/df89b724-3201-47aa-b8cd-282e112a566fExploit, Issue Tracking, Patch, Third Party Advisory
• https://lists.apache.org/thread/ky1ssskvkj00y36k7nys9b5gm5jjrzwvIssue Tracking, Mailing List, Vendor Advisory
• https://huntr.dev/bounties/df89b724-3201-47aa-b8cd-282e112a566fExploit, Issue Tracking, Patch, Third Party Advisory
• https://lists.apache.org/thread/ky1ssskvkj00y36k7nys9b5gm5jjrzwvIssue Tracking, Mailing List, Vendor Advisory

Published

Nov 4, 2022

Last Modified

Jun 17, 2026

Status

Modified

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2022-33679Windows Kerberos Elevation of Privilege Vulnerability8.1
• CVE-2022-3368A vulnerability within the Software Updater functionality of…8.8
• CVE-2022-33680Microsoft Edge (Chromium-based) Elevation of Privilege Vulne…8.3
• CVE-2022-33681Delayed TLS hostname verification in the Pulsar Java Client …5.9
• CVE-2022-33682TLS hostname verification cannot be enabled in the Pulsar Br…5.9
• CVE-2022-33683Apache Pulsar Brokers and Proxies create an internal Pulsar …5.9
• CVE-2022-33685Unprotected dynamic receiver in Wearable Manager Service pri…5.5
• CVE-2022-33686Exposure of Sensitive Information in GsmAlarmManager prior t…2.3
• CVE-2022-33687Exposure of Sensitive Information in telephony-common.jar pr…3.3
• CVE-2022-33688Sensitive information exposure vulnerability in EventType in…3.3
• CVE-2022-33689Improper access control vulnerability in TelephonyUI prior t…3.3
• CVE-2022-3369An Improper Access Control vulnerability in the bdservicehos…5.5