Description
Apache Pulsar Brokers and Proxies create an internal Pulsar Admin Client that does not verify peer TLS certificates, even when tlsAllowInsecureConnection is disabled via configuration. The Pulsar Admin Client's intra-cluster and geo-replication HTTPS connections are vulnerable to man in the middle attacks, which could leak authentication data, configuration data, and any other data sent by these clients. 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. This issue affects Apache Pulsar Broker and 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.
Remediation
References
https://lists.apache.org/thread/42v5rsxj36r3nhfxhmhb2x12r5jmvx3x
Related Vulnerabilities
CVE-2017-14063 Vulnerability in maven package org.asynchttpclient:async-http-client
CVE-2019-3774 Vulnerability in maven package org.springframework.batch:spring-batch-core
CVE-2020-15250 Vulnerability in maven package junit:junit
CVE-2020-13953 Vulnerability in maven package org.apache.tapestry:tapestry-core
CVE-2023-49803 Vulnerability in maven package org.webjars.npm:koa__cors