PinotApplication · Apache
CVE-2024-56325
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 · uneditedAuthentication Bypass Issue If the path does not contain / and contain., authentication is not required. Expected Normal Request and Response Example curl -X POST -H "Content-Type: application/json" -d {\"username\":\"hack2\",\"password\":\"hack\",\"component\":\"CONTROLLER\",\"role\":\"ADMIN\",\"tables\":[],\"permissions\":[],\"usernameWithComponent\":\"hack_CONTROLLER\"} http://{server_ip}:9000/users Return: {"code":401,"error":"HTTP 401 Unauthorized"} Malicious Request and Response Example curl -X POST -H "Content-Type: application/json" -d '{\"username\":\"hack\",\"password\":\"hack\",\"component\":\"CONTROLLER\",\"role\":\"ADMIN\",\"tables\":[],\"permissions\":[],\"usernameWithComponent\":\"hack_CONTROLLER\"}' http://{serverip}:9000/users; http://{serverip}:9000/users; . Return: {"users":{}} A new user gets added bypassing authentication, enabling the user to control Pinot.
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 · moderate confidenceApache Pinot contains an authentication bypass vulnerability where the authentication logic incorrectly evaluates request paths. If a path does not contain a forward slash and contains a period, the authentication check is skipped. Attackers can exploit this by crafting paths with semicolons and trailing periods (e.g., '/users; .') to bypass authentication entirely and create administrative users, gaining full control over the Pinot system.
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
< 1.3.0CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify Apache Pinot versionCheck the Pinot version by inspecting the Pinot controller or broker process, typically found in the pom.xml, or query the Pinot controller API at /version or /health (if accessible)Affected if The installed version is Apache Pinot prior to 1.3.0
-
Confirm management port accessibilityVerify if port 9000 (Pinot controller management port) is exposed to the network. Use 'netstat -tlnp | grep 9000' or 'ss -tlnp | grep 9000' to check listening status, and check firewall rules or network configuration for external accessibilityAffected if Port 9000 is listening and accessible from untrusted networks
-
Verify authentication configurationInspect the Pinot controller configuration file (typically controller.conf) for authentication settings. Look for 'controller.access.control' configuration or related authentication enablement flagsAffected if Authentication is not explicitly enabled in the configuration, or default credentials are in use
-
Test path-based authentication bypassIf authentication is enabled, attempt a request to a path that does not contain a forward slash but contains a period and semicolon (e.g., using a tool like curl to send a request to '/users; .' endpoint) to see if authentication is enforcedAffected if The authentication check is bypassed for paths without forward slashes that contain periods (semicolon pattern)
-
Check for unauthorized admin usersQuery the Pinot user/tenant API (if accessible) to list administrative users and verify if any unexpected or unauthorized administrator accounts existAffected if Unexpected administrative users are present that were not created by authorized administrators
A user is affected if they are running Apache Pinot version prior to 1.3.0 with port 9000 exposed to untrusted networks and authentication potentially bypassed via the path manipulation technique.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.3.0
Apply the vendor patch when available. Until then, restrict network access to the Pinot management port (9000) to trusted IPs only using firewall rules or network segmentation, as the vulnerable endpoint handles user management.
Apache Pinot 1.3.0
- 1. Stop the Pinot cluster or the affected Pinot services
- 2. Ensure you have a backup of your Pinot configuration and data
- 3. Upgrade Apache Pinot to version 1.3.0 or later
- 4. Restart the Pinot controller and broker services
- 5. Verify the fix by attempting the vulnerable request pattern (e.g., curl http://{server_ip}:9000/users; .) - it should now return 401 Unauthorized instead of bypassing authentication
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
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-56325 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-56325 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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