# CVE-2024-39676: Apache Pinot: Unauthorized endpoint exposed sensitive information > Unauthorized access to the /appconfigs endpoint exposes sensitive system and configuration data in Apache Pinot. - **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 24 Jul 2024 - **Updated:** 14 Mar 2025 - **Also known as:** GHSA-8gj9-r4hv-3jjw ## What is CVE-2024-39676? CVE-2024-39676 is a high-severity vulnerability in Apache Pinot, published on 24 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description 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. Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) ## Which versions are affected by CVE-2024-39676? 2 open source packages ship an affected version, including org.apache.pinot:pinot-controller. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.apache.pinot:pinot-controller` | Maven | From 0.1 | 1.0.0 | | `org.apache.pinot:pinot-controller` | Maven | From 0.1 | 1.0.0 | Products: Apache Pinot. ## How do I fix CVE-2024-39676? Upgrade org.apache.pinot:pinot-controller to 1.0.0 or later. ## Is CVE-2024-39676 being exploited? There is no known exploitation of CVE-2024-39676 in the wild and no public exploit code. ## Other vulnerabilities in Apache Pinot - [CVE-2024-56325](https://insights.sbomify.com/CVE-2024-56325/): Apache Pinot: Authentication bypass issue. If the path does not contain / and contain . authentication is not required (critical 9.8) - [CVE-2022-26112](https://insights.sbomify.com/CVE-2022-26112/): Apache Pinot has Groovy Function support enabled by default (critical 9.8) - [CVE-2022-23974](https://insights.sbomify.com/CVE-2022-23974/): Pinot segment push endpoint has a vulnerability in unprotected environments (high 7.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-39676 and fix it if it is affected. What it is: CVE-2024-39676 is a high-severity vulnerability in Apache Pinot, published on 24 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2024-39676 in the wild and no public exploit code. Affected packages and fixed versions: - org.apache.pinot:pinot-controller (Maven): affected from 0.1; fixed in 1.0.0 - org.apache.pinot:pinot-controller (Maven): affected from 0.1; fixed in 1.0.0 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2024-39676/ (Markdown: https://insights.sbomify.com/CVE-2024-39676/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-39676 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-39676 - OSV: https://osv.dev/vulnerability/CVE-2024-39676 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-39676/ Summaries are generated and may contain mistakes; the official description above is the record.