GHSA-jvf3-mfxv-jcqr

    Dashboard / Vulnerabilities / GHSA-jvf3-mfxv-jcqr

    GHSA-jvf3-mfxv-jcqr

    Published: 25 Sept 2022Last Modified: 8 Nov 2023

    Summary: Apache Pulsar Broker, Proxy, and WebSocket Proxy vulnerable to Improper Certificate Validation

    Details: 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.

    Affected packages

    Package

    Name: org.apache.pulsar:pulsar-broker

    Purl: pkg:maven/org.apache.pulsar/pulsar-broker

    Affected ranges

    Type: ECOSYSTEM

    Events:

    Introduced- 0
    Fixed -2.7.5

    Affected versions

    1.19.0-incubating

    Common Vulnerability Scoring System

    Attack Vector
    Network
    Adjacent
    Local
    Physical
    Privileges Required
    None
    Low
    High
    User Interaction
    None
    Required
    Scope
    Unchanged
    Changed
    Confidentiality
    None
    Low
    High
    Integrity
    None
    Low
    High
    Availability
    None
    Low
    High
    GHSA-jvf3-mfxv-jcqr | CVE-DB