Apache Druid: The HTTP inputSource allows authenticated users to read data from other sources than intended
Apache Software Foundation Apache Druid
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.druid:druid-core Maven |
|
|
| fast-xml-parser npm |
|
|
Apache Software Foundation Apache Druid
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.druid:druid-core Maven |
|
|
| fast-xml-parser npm |
|
|
In the Druid ingestion system, the InputSource is used for reading data from a certain data source. However, the HTTP InputSource allows authenticated users to read data from other sources than intended, such as the local file system, with the privileges of the Druid server process. This is not an elevation of privilege when users access Druid directly, since Druid also provides the Local InputSource, which allows the same level of access. But it is problematic when users interact with Druid indirectly through an application that allows users to specify the HTTP InputSource, but not the Local InputSource. In this case, users could bypass the application-level restriction by passing a file URL to the HTTP InputSource.
From the CVE record · apache
Apache Druid's HTTP InputSource can read from sources other than those intended, including the local file system, with the privileges of the Druid server process. An authenticated user can bypass an application-level restriction on Local InputSource by supplying a file URL to HTTP InputSource when the application permits the latter but not the former.
Check deployments using Apache Druid's Maven package org.apache.druid:druid-core before 0.21.0 and installations of the listed npm package fast-xml-parser before 4.1.2.