ghsa-j3qw-g67q-7m64
Vulnerability from github
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.
{ affected: [ { package: { ecosystem: "Maven", name: "org.apache.pulsar:pulsar-broker", }, ranges: [ { events: [ { introduced: "0", }, { fixed: "2.7.5", }, ], type: "ECOSYSTEM", }, ], }, { package: { ecosystem: "Maven", name: "org.apache.pulsar:pulsar-proxy", }, ranges: [ { events: [ { introduced: "0", }, { fixed: "2.7.5", }, ], type: "ECOSYSTEM", }, ], }, { package: { ecosystem: "Maven", name: "org.apache.pulsar:pulsar-broker", }, ranges: [ { events: [ { introduced: "2.8.0", }, { fixed: "2.8.4", }, ], type: "ECOSYSTEM", }, ], }, { package: { ecosystem: "Maven", name: "org.apache.pulsar:pulsar-proxy", }, ranges: [ { events: [ { introduced: "2.8.0", }, { fixed: "2.8.4", }, ], type: "ECOSYSTEM", }, ], }, { package: { ecosystem: "Maven", name: "org.apache.pulsar:pulsar-broker", }, ranges: [ { events: [ { introduced: "2.9.0", }, { fixed: "2.9.3", }, ], type: "ECOSYSTEM", }, ], }, { package: { ecosystem: "Maven", name: "org.apache.pulsar:pulsar-proxy", }, ranges: [ { events: [ { introduced: "2.9.0", }, { fixed: "2.9.3", }, ], type: "ECOSYSTEM", }, ], }, { package: { ecosystem: "Maven", name: "org.apache.pulsar:pulsar-broker", }, ranges: [ { events: [ { introduced: "2.10.0", }, { fixed: "2.10.1", }, ], type: "ECOSYSTEM", }, ], versions: [ "2.10.0", ], }, { package: { ecosystem: "Maven", name: "org.apache.pulsar:pulsar-proxy", }, ranges: [ { events: [ { introduced: "2.10.0", }, { fixed: "2.10.1", }, ], type: "ECOSYSTEM", }, ], versions: [ "2.10.0", ], }, ], aliases: [ "CVE-2022-33683", ], database_specific: { cwe_ids: [ "CWE-295", ], github_reviewed: true, github_reviewed_at: "2022-09-30T04:26:00Z", nvd_published_at: "2022-09-23T10:15:00Z", severity: "MODERATE", }, details: "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.", id: "GHSA-j3qw-g67q-7m64", modified: "2022-09-30T04:26:00Z", published: "2022-09-25T00:00:27Z", references: [ { type: "ADVISORY", url: "https://nvd.nist.gov/vuln/detail/CVE-2022-33683", }, { type: "WEB", url: "https://lists.apache.org/thread/42v5rsxj36r3nhfxhmhb2x12r5jmvx3x", }, ], schema_version: "1.4.0", severity: [ { score: "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N", type: "CVSS_V3", }, ], summary: "Apache Pulsar Brokers and Proxies vulnerable to Improper Certificate Validation", }
Log in or create an account to share your comment.
This schema specifies the format of a comment related to a security advisory.
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.