GHSA-c35h-w8hj-mm55

Source

https://github.com/advisories/GHSA-c35h-w8hj-mm55

Import Source

https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2024/03/GHSA-c35h-w8hj-mm55/GHSA-c35h-w8hj-mm55.json

JSON Data

https://api.test.osv.dev/v1/vulns/GHSA-c35h-w8hj-mm55

Aliases

CVE-2022-34321

Published

2024-03-12T21:30:59Z

Modified

2024-05-02T18:47:09.157653Z

Severity

8.2 (High) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L CVSS Calculator

Summary

Apache Pulsar: Improper Authentication for Pulsar Proxy Statistics Endpoint

Details

Improper Authentication vulnerability in Apache Pulsar Proxy allows an attacker to connect to the /proxy-stats endpoint without authentication. The vulnerable endpoint exposes detailed statistics about live connections, along with the capability to modify the logging level of proxied connections without requiring proper authentication credentials.

This issue affects Apache Pulsar versions from 2.6.0 to 2.10.5, from 2.11.0 to 2.11.2, from 3.0.0 to 3.0.1, and 3.1.0.

The known risks include exposing sensitive information such as connected client IP and unauthorized logging level manipulation which could lead to a denial-of-service condition by significantly increasing the proxy's logging overhead. When deployed via the Apache Pulsar Helm chart within Kubernetes environments, the actual client IP might not be revealed through the load balancer's default behavior, which typically obscures the original source IP addresses when externalTrafficPolicy is being configured to "Cluster" by default. The /proxy-stats endpoint contains topic level statistics, however, in the default configuration, the topic level statistics aren't known to be exposed.

2.10 Pulsar Proxy users should upgrade to at least 2.10.6. 2.11 Pulsar Proxy users should upgrade to at least 2.11.3. 3.0 Pulsar Proxy users should upgrade to at least 3.0.2. 3.1 Pulsar Proxy users should upgrade to at least 3.1.1.

Users operating versions prior to those listed above should upgrade to the aforementioned patched versions or newer versions. Additionally, it's imperative to recognize that the Apache Pulsar Proxy is not intended for direct exposure to the internet. The architectural design of Pulsar Proxy assumes that it will operate within a secured network environment, safeguarded by appropriate perimeter defenses.

Database specific

{
    "nvd_published_at": "2024-03-12T19:15:47Z",
    "cwe_ids": [
        "CWE-306"
    ],
    "severity": "HIGH",
    "github_reviewed": true,
    "github_reviewed_at": "2024-03-13T21:58:52Z"
}

References

Affected packages

Maven / org.apache.pulsar:pulsar-proxy

Package

Name: org.apache.pulsar:pulsar-proxy; View open source insights on deps.dev
Purl: pkg:maven/org.apache.pulsar/pulsar-proxy

Affected ranges

Type: ECOSYSTEM
Events: Introduced

2.6.0

Fixed

2.10.6

Affected versions

2.*

2.6.0

2.6.1

2.6.2

2.6.3

2.6.4

2.7.0

2.7.1

2.7.2

2.7.3

2.7.4

2.7.5

2.8.0

2.8.1

2.8.2

2.8.3

2.8.4

2.9.0

2.9.1

2.9.2

2.9.3

2.9.4

2.9.5

2.10.0

2.10.1

2.10.2

2.10.3

2.10.4

2.10.5

Database specific

{
    "last_known_affected_version_range": "<= 2.10.5"
}

Maven / org.apache.pulsar:pulsar-proxy

Package

Name: org.apache.pulsar:pulsar-proxy; View open source insights on deps.dev
Purl: pkg:maven/org.apache.pulsar/pulsar-proxy

Affected ranges

Type: ECOSYSTEM
Events: Introduced

2.11.0

Fixed

2.11.3

Affected versions

2.*

2.11.0

2.11.1

2.11.2

Database specific

{
    "last_known_affected_version_range": "<= 2.11.2"
}

Maven / org.apache.pulsar:pulsar-proxy

Package

Name: org.apache.pulsar:pulsar-proxy; View open source insights on deps.dev
Purl: pkg:maven/org.apache.pulsar/pulsar-proxy

Affected ranges

Type: ECOSYSTEM
Events: Introduced

3.0.0

Fixed

3.0.2

Affected versions

3.*

3.0.0

3.0.1

Database specific

{
    "last_known_affected_version_range": "<= 3.0.1"
}