ghsa-jvf3-mfxv-jcqr
Vulnerability from github
Published
2022-09-25 00:00
Modified
2022-09-30 00:09
Severity ?
5.9 (Medium) - CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
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.

Show details on source website

To clipboard 

{
   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-33682",
   ],
   database_specific: {
      cwe_ids: [
         "CWE-295",
      ],
      github_reviewed: true,
      github_reviewed_at: "2022-09-30T00:09:24Z",
      nvd_published_at: "2022-09-23T10:15:00Z",
      severity: "MODERATE",
   },
   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.",
   id: "GHSA-jvf3-mfxv-jcqr",
   modified: "2022-09-30T00:09:24Z",
   published: "2022-09-25T00:00:27Z",
   references: [
      {
         type: "ADVISORY",
         url: "https://nvd.nist.gov/vuln/detail/CVE-2022-33682",
      },
      {
         type: "WEB",
         url: "https://lists.apache.org/thread/l0ynfl161qghwfcgbbl8ld9hzbl9t3yx",
      },
   ],
   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 Broker, Proxy, and WebSocket Proxy vulnerable to Improper Certificate Validation",
}


Log in or create an account to share your comment.

Security Advisory comment format.

This schema specifies the format of a comment related to a security advisory.

UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).



Tags
Taxonomy of the tags.




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.