CVE-2024-23768
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 · uneditedDremio before 24.3.1 allows path traversal. An authenticated user who has no privileges on certain folders (and the files and datasets in these folders) can access these folders, files, and datasets. To be successful, the user must have access to the source and at least one folder in the source. Affected versions are: 24.0.0 through 24.3.0, 23.0.0 through 23.2.3, and 22.0.0 through 22.2.2. Fixed versions are: 24.3.1 and later, 23.2.4 and later, and 22.2.3 and later.
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 confidenceDremio before 24.3.1 contains a path traversal vulnerability allowing authenticated users to bypass folder access controls. Users with source access and at least one folder privilege can traverse paths to access restricted folders, files, and datasets they should not have permissions to view.
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>= 22.0.0, < 22.2.3>= 23.0.0, < 23.2.4>= 24.0.0, < 24.3.1CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 Dremio versionCheck the Dremio version through the web UI (typically displayed on the login page or in the admin settings) or by querying the Dremio metadata serviceAffected if The installed version falls within one of these ranges: 22.0.0 to 22.2.2, 23.0.0 to 23.2.3, or 24.0.0 to 24.3.0
-
Confirm authentication is enabledVerify that Dremio user authentication is configured and active. Check the authentication settings in the Dremio admin consoleAffected if Authentication is enabled and users can log in to the system
-
Verify folder access controls existReview the folder and dataset access control configurations in Dremio. Check if folder-level permissions are defined for users or groupsAffected if Folder access controls are configured and users have source access with at least one folder privilege
-
Check for path traversal in dataset pathsAudit dataset and folder paths in the Dremio catalog. Look for paths containing sequences like ../ or unusual path structures that could indicate traversal attemptsAffected if Any dataset paths reference directories outside the intended folder hierarchy
A user is affected if they are running a Dremio version in the ranges 22.0.0-22.2.2, 23.0.0-23.2.3, or 24.0.0-24.3.0 with authentication and folder access controls configured, as the path traversal flaw allows bypassing those controls.
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 · scoped22.2.323.2.424.3.1
Upgrade Dremio to version 24.3.1, 23.2.4, or 22.2.3 or later. If immediate upgrade is not feasible, implement additional path validation and access control enforcement at the application layer.
24.3.1 (or 23.2.4 or 22.2.3 depending on current version branch)
- 1. Identify the current Dremio version by checking the Dremio UI or running `dremio --version`
- 2. Determine the appropriate upgrade path based on current version: if 22.0.x-22.2.2 upgrade to 22.2.3+, if 23.0.x-23.2.3 upgrade to 23.2.4+, if 24.0.x-24.3.0 upgrade to 24.3.1+
- 3. Create a full backup of the Dremio metadata store, configuration files, and any custom scripts
- 4. Stop the Dremio service gracefully
- 5. Download the appropriate fixed version from the official Dremio downloads page
- 6. Install the upgrade following Dremio's standard upgrade procedure for your deployment type
- 7. Start the Dremio service and verify successful startup
- 8. Log in as an authenticated user and confirm the path traversal vulnerability is mitigated by attempting to access restricted folders using traversal sequences (e.g., ../../)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing8.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 $5,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-23768 — 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-23768 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