dbcve.org
PinotApplication · Apache

CVE-2022-23974

HIGH · 7.5 CVSS v3.1 Published 2022-04-05
Fix available
A fix is available. Upgrade to 0.10.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
In 0.9.3 or older versions of Apache Pinot segment upload path allowed segment directories to be imported into pinot tables. In pinot installations that allow open access to the controller a specially crafted request can potentially be exploited to cause disruption in pinot service. Pinot release 0.10.0 fixes this. See https://docs.pinot.apache.org/basics/releases/0.10.0

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

Apache Pinot versions 0.9.3 and older contain a path traversal vulnerability in the segment upload functionality that allows importing segment directories into tables. When the controller is exposed with open access (no authentication), an attacker can send specially crafted requests containing malicious segment directory paths to achieve arbitrary file placement and cause service disruption.

MitigationUpgrade Apache Pinot to version 0.10.0 or later, and ensure the controller is not exposed to unauthenticated access by implementing proper authentication and authorization controls.

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.10.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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checks

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

  1. Identify Apache Pinot version
    Check the Pinot controller or broker version. This can typically be found in the Pinot UI (Admin Dashboard) under 'Cluster' > 'Node Details', or by checking the version file in the Pinot installation directory if accessible, or via the /version REST API endpoint on the controller.
    Affected if The installed version is older than 0.10.0 (e.g., 0.9.3, 0.9.2, etc.)
  2. Verify controller authentication is enabled
    Check the Pinot controller configuration file (controller.conf) for the presence and proper configuration of authentication-related properties such as 'access.control.allowed.tables', 'access.control.authentication' or 'pinot.controller.administrator.token' or similar authentication provider settings. Also check if the controller starts with any security-related flags.
    Affected if Authentication is not configured or is explicitly disabled in the controller configuration, allowing unauthenticated access to the segment upload endpoint.
  3. Inspect network exposure of the controller
    Review network configuration, firewall rules, or Kubernetes/service definitions to determine if the Pinot controller API port (typically 9000 or 8097) is exposed to untrusted networks or the public internet without authentication or network-level access controls.
    Affected if The controller is accessible from untrusted networks without requiring authentication, enabling an attacker to reach the segment upload functionality.
  4. Confirm segment upload endpoint accessibility
    Test reachability of the segment upload API endpoint (typically /segments or /controller/segments) on the Pinot controller without providing any credentials. Use a curl or similar request to probe the endpoint.
    Affected if The endpoint returns a successful response without requiring authentication, indicating open access.

You are affected if your Apache Pinot version is below 0.10.0 AND the controller is exposed without authentication, allowing unauthenticated access to the segment upload functionality.

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 0.10.0 or later
Fixed in 0.10.0
Interim mitigation

Upgrade Apache Pinot to version 0.10.0 or later, and ensure the controller is not exposed to unauthenticated access by implementing proper authentication and authorization controls.

Recommended fix High confidence

0.10.0

  1. Upgrade Apache Pinot to version 0.10.0 or later
  2. Verify the upgrade by reviewing release notes at https://docs.pinot.apache.org/basics/releases/0.10.0
  3. Test segment upload functionality after upgrade to confirm the vulnerability is remediated
Caveat Review release notes for any deprecations or breaking changes between your current version and 0.10.0

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
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-23974 — 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-2022-23974 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