dbcve.org
DorisApplication · Apache

CVE-2024-48019

MEDIUM · 5.4 CVSS v3.1 Published 2025-02-04
Fix available
A fix is available. Upgrade to 2.1.8 / 3.0.3 or later.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable 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
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'), Files or Directories Accessible to External Parties vulnerability in Apache Doris. Application administrators can read arbitrary files from the server filesystem through path traversal. Users are recommended to upgrade to version 2.1.8, 3.0.3 or later, which fixes the issue.

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 confidence

Apache Doris contains a path traversal vulnerability that allows authenticated administrators to read arbitrary files from the server filesystem by manipulating file paths in certain operations. This improper limitation of pathname to restricted directory enables unauthorized file system access.

MitigationUpgrade Apache Doris to version 2.1.8, 3.0.3, or later to remediate this vulnerability. Restrict administrative access to trusted personnel as an interim control.

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
DorisApplication
Affected:>= 2.1.0, < 2.1.8>= 3.0.0, < 3.0.3

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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 Doris version
    Run 'select version();' in the MySQL client connected to Doris, or check the fe.log file for the version string
    Affected if The version shown is between 2.1.0 and 2.1.7, or between 3.0.0 and 3.0.2
  2. Confirm file operation feature is accessible
    Check if the web UI (port 8030) or MySQL protocol port (9030) administrative interface is reachable and operational
    Affected if Administrative interface is exposed and accessible to the evaluator
  3. Verify administrative user exists
    Check for admin-role users in Doris via 'SHOW GRANTS;' query or through user configuration files
    Affected if There exists at least one user with administrative privileges who could trigger the vulnerable file operation
  4. Check if file export/load operations are permitted
    Review Doris configuration (fe.conf) for OUTFILE or file-related export/load permissions, or check if the file_broker feature is loaded
    Affected if File export, load through broker, or similar file-path-involving operations are enabled for administrative users

You are affected if your Apache Doris version falls within 2.1.0-2.1.7 or 3.0.0-3.0.2 AND administrative users with file operation capabilities can access the system.

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 2.1.8 / 3.0.3 or later
Fixed in 2.1.83.0.3
Interim mitigation

Upgrade Apache Doris to version 2.1.8, 3.0.3, or later to remediate this vulnerability. Restrict administrative access to trusted personnel as an interim control.

Recommended fix High confidence

2.1.8 for 2.1.x branches; 3.0.3 for 3.0.x branches

  1. 1. Backup all Doris data and configuration files before upgrading
  2. 2. Determine your current Doris version using: `select version();`
  3. 3. If running version 2.1.x (between 2.1.0 and 2.1.7), plan upgrade to version 2.1.8
  4. 4. If running version 3.0.x (between 3.0.0 and 3.0.2), plan upgrade to version 3.0.3
  5. 5. Review the official Apache Doris upgrade documentation at https://doris.apache.org/docs/admin-manual/cluster-management/upgrade/
  6. 6. Follow the standard rolling upgrade procedure for your deployment method (manual or FE/BE rolling upgrade)
  7. 7. After upgrade, verify the fix by confirming the new version: `select version();` returns 2.1.8 or 3.0.3
  8. 8. Test that the path traversal vulnerability is no longer exploitable
Caveat Review release notes for 2.1.8 and 3.0.3 to check for any breaking changes specific to your deployment; standard Doris rolling upgrades are generally safe

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

Fix this in Doris Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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