The Apache Pulsar C++ Client and Python Client do not verify peer TLS certificates when making HTTPS calls for the OAuth2.0 Client Credential Flow, even when `tlsAllowInsecureConnection` is disabled via configuration. This allows an attacker to perform a man-in-the-middle attack and intercept and/or modify the GET request 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 must take control of a machine "between" the client and the server and actively manipulate traffic to perform the attack.