dbcve.org
DrillApplication · Apache

CVE-2023-48362

HIGH · 8.8 CVSS v3.1 Published 2024-07-24
Fix available
A fix is available. Upgrade to 1.21.2 or later.
See remediation →
94/100
Remediation priority · Urgent
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
XXE in the XML Format Plugin in Apache Drill version 1.19.0 and greater allows a user to read any file on a remote file system or execute commands via a malicious XML file. Users are recommended to upgrade to version 1.21.2, which fixes this 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 · high confidence

A critical XXE (XML External Entity) vulnerability in Apache Drill's XML Format Plugin allows authenticated users to read arbitrary files from the remote file system or execute arbitrary commands by supplying specially crafted malicious XML files. The vulnerability affects versions 1.19.0 through 1.21.1.

MitigationUpgrade Apache Drill to version 1.21.2 or later, which contains the fix for this XXE vulnerability in the XML Format Plugin.

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
DrillApplication
Affected:>= 1.9.0, < 1.21.2

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
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 checks

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

  1. Identify Apache Drill version
    Check the installed Drill version by examining the release notes file, the drill-common JAR manifest, or by running 'drill-embedded' and looking for the version output
    Affected if Version is 1.9.0 through 1.21.1 (inclusive)
  2. Verify XML Format Plugin is enabled
    Review Drill storage plugin configuration files (usually in the /drill/storagePlugins/ directory or through the Drill web UI at port 8047) for any XML format plugin definitions
    Affected if An XML format plugin is configured and active
  3. Confirm XML file queries are possible
    Check if queries using XML format are being executed, such as SELECT statements against XML files using the xml storage plugin (e.g., SELECT * FROM xml.`path/to/file.xml`)
    Affected if Users can query or load XML files through Drill

If Apache Drill version is 1.9.0 through 1.21.1 and the XML Format Plugin is enabled or being used to process XML files, the environment is affected by this XXE vulnerability.

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

Upgrade Apache Drill to version 1.21.2 or later, which contains the fix for this XXE vulnerability in the XML Format Plugin.

Recommended fix High confidence

1.21.2

  1. Identify the current Apache Drill version in use (check via drill --version or the web UI)
  2. Stop all Drill services (drillbit) to prevent data corruption during upgrade
  3. Back up the Drill installation directory, including configuration files in conf/ and any custom storage plugins
  4. Download Apache Drill version 1.21.2 from the official Apache Drill distribution (https://drill.apache.org/download/)
  5. Extract the new version to the desired installation location
  6. Copy or merge custom configuration files from the backup to the new installation (review conf/drill-override.conf for custom settings)
  7. Verify file permissions are correctly set for the new installation
  8. Start the Drill service (drillbit)

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

Fix this in Drill Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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