dbcve.org
DorisApplication · Apache

CVE-2023-41314

HIGH · 8.2 CVSS v3.1 Published 2023-12-18
Fix available
A fix is available. Upgrade to 2.0.3 or later.
See remediation →
91/100
Remediation priority · Urgent
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
The api /api/snapshot and /api/get_log_file would allow unauthenticated access. It could allow a DoS attack or get arbitrary files from FE node. Please upgrade to 2.0.3 to fix these issues.

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

Two API endpoints (/api/snapshot and /api/get_log_file) in the application lack authentication controls, allowing any unauthenticated user to access them. This could enable attackers to read arbitrary files from the frontend node or cause denial of service.

MitigationUpgrade to version 2.0.3 which adds proper authentication to these endpoints.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 Doris version
    Run 'select version()' via MySQL client connected to Doris FE, or check the FE log file for version strings at startup
    Affected if version shown is lower than 2.0.3 (e.g., 2.0.2, 2.0.1, 1.x series)
  2. Verify /api/snapshot endpoint accessibility
    Send an unauthenticated HTTP GET request to http://<doris-fe-host>:<http-port>/api/snapshot
    Affected if endpoint returns a response (rather than 401/403 authentication error) and may expose file content or system information
  3. Verify /api/get_log_file endpoint accessibility
    Send an unauthenticated HTTP GET request to http://<doris-fe-host>:<http-port>/api/get_log_file with a path parameter
    Affected if endpoint returns log file contents or file listing without requiring authentication credentials
  4. Check FE http port exposure
    Identify the Doris FE http port from fe.conf (property: http_port, default 8030) and confirm it is reachable from untrusted networks
    Affected if http port is exposed externally without network ACLs filtering /api/ endpoints

User is affected if running Apache Doris version lower than 2.0.3 AND the /api/snapshot or /api/get_log_file endpoints respond to unauthenticated requests without returning authentication errors.

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.0.3 or later
Fixed in 2.0.3
Interim mitigation

Upgrade to version 2.0.3 which adds proper authentication to these endpoints.

Recommended fix High confidence

2.0.3

  1. 1. Backup your current Doris deployment and database data
  2. 2. Review the Apache Doris 2.0.3 release notes for any migration requirements or breaking changes
  3. 3. Download Apache Doris 2.0.3 from the official Apache repository (https://doris.apache.org/download/)
  4. 4. Stop all running Doris FE (Frontend) and BE (Backend) nodes
  5. 5. Replace the existing Doris binaries with version 2.0.3
  6. 6. Upgrade FE nodes first, starting with the follower nodes, then the leader
  7. 7. After FE upgrade is complete, upgrade BE nodes
  8. 8. Verify that the /api/snapshot and /api/get_log_file endpoints now require authentication
Caveat Review Apache Doris 2.0.3 release notes; major version upgrades may include schema or configuration changes that require migration steps

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

Fix this in Doris Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
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,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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