dbcve.org
PinotApplication · Apache

CVE-2024-39676

HIGH · 7.5 CVSS v3.1 Published 2024-07-24
Fix available
A fix is available. Upgrade to 1.0.0 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Exposure of Sensitive Information to an Unauthorized Actor vulnerability in Apache Pinot. This issue affects Apache Pinot: from 0.1 before 1.0.0. Users are recommended to upgrade to version 1.0.0 and configure RBAC, which fixes the issue. Details:  When using a request to path “/appconfigs” to the controller, it can lead to the disclosure of sensitive information such as system information (e.g. arch, os version), environment information (e.g. maxHeapSize) and Pinot configurations (e.g. zookeeper path). This issue was addressed by the Role-based Access Control https://docs.pinot.apache.org/operators/tutorials/authentication/basic-auth-access-control , so that /appConfigs` and all other APIs can be access controlled. Only authorized users have access to it. Note the user needs to add the admin role accordingly to the RBAC guide to control access to this endpoint, and in the future version of Pinot, a default admin role is planned to be added.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The /appconfigs endpoint in Apache Pinot versions before 1.0.0 exposes sensitive system information (OS version, architecture), environment variables (heap size), and internal configuration (Zookeeper path) to unauthenticated users. This information disclosure could aid attackers in reconnaissance and further exploitation.

MitigationUpgrade Apache Pinot to version 1.0.0 or later and configure Role-based Access Control (RBAC) to restrict access to the /appConfigs endpoint and other sensitive APIs, assigning appropriate admin roles per the RBAC documentation.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
PinotApplication
Affected:>= 0.1.0, < 1.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Apache Pinot installation and version
    Locate the Pinot installation directory and check the version file or use the pinot-admin.sh version command. Common locations include /opt/pinot or /usr/local/pinot. The version is typically found in a VERSION or version.txt file in the installation root.
    Affected if The installed version is 0.1.0 or higher but lower than 1.0.0.
  2. Confirm the /appconfigs endpoint is accessible
    Send an HTTP GET request to http://<pinot-controller-host>:<port>/appconfigs without providing any authentication credentials. Use curl or a similar tool.
    Affected if The endpoint returns HTTP 200 with system information (OS version, architecture, environment variables like heap size, Zookeeper path) without requiring authentication.
  3. Verify if RBAC is enabled
    Check the Pinot controller configuration file (typically controller.conf) for the security.admin.type setting or look for RBAC-related configuration. Also check if the /appconfigs endpoint is explicitly secured in the access control list.
    Affected if RBAC is not enabled or not configured to restrict access to /appconfigs, meaning the endpoint remains exposed to unauthenticated users.

A user is affected if they run Apache Pinot version 0.1.0 through 0.9.x with the /appconfigs endpoint accessible without authentication and without RBAC protection in place.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.0.0 or later
Fixed in 1.0.0
Interim mitigation

Upgrade Apache Pinot to version 1.0.0 or later and configure Role-based Access Control (RBAC) to restrict access to the /appConfigs endpoint and other sensitive APIs, assigning appropriate admin roles per the RBAC documentation.

Recommended fix High confidence

1.0.0

  1. 1. Upgrade Apache Pinot from any version < 1.0.0 to version 1.0.0
  2. 2. Enable and configure Role-based Access Control (RBAC) for the Pinot controller following the documentation at https://docs.pinot.apache.org/operators/tutorials/authentication/basic-auth-access-control
  3. 3. Add the admin role to appropriate users to control access to the /appConfigs endpoint and other sensitive APIs
Caveat Review RBAC configuration requirements and update authentication/authorization policies before deployment to production

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Pinot Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-39676 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-39676 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data