CVSS3
Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality Impact
NONE
Integrity Impact
HIGH
Availability Impact
HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
AI Score
Confidence
High
EPSS
Percentile
18.1%
MindsDB is a SQL Server for artificial intelligence. Prior to version 23.11.4.1, the put
method in mindsdb/mindsdb/api/http/namespaces/file.py
does not validate the user-controlled name value, which is used in a temporary file name, which is afterwards opened for writing on lines 122-125, which leads to path injection. Later in the method, the temporary directory is deleted on line 151, but since we can write outside of the directory using the path injection vulnerability, the potentially dangerous file is not deleted. Arbitrary file contents can be written due to f.write(chunk)
on line 125. Mindsdb does check later on line 149 in the save_file
method in file-controller.py
which calls the _handle_source
method in file_handler.py
if a file is of one of the types csv
, json
, parquet
, xls
, or xlsx
. However, since the check happens after the file has already been written, the files will still exist (and will not be removed due to the path injection described earlier), just the _handle_source
method will return an error. The same user-controlled source source is used also in another path injection sink on line 138. This leads to another path injection, which allows an attacker to delete any zip
or tar.gz
files on the server.
[
{
"vendor": "mindsdb",
"product": "mindsdb",
"versions": [
{
"version": "< 23.11.4.1",
"status": "affected"
}
]
}
]
github.com/mindsdb/mindsdb/blob/1821da719f34c022890c9ff25810218e71c5abbc/mindsdb/api/http/namespaces/file.py#L122-L125
github.com/mindsdb/mindsdb/blob/1821da719f34c022890c9ff25810218e71c5abbc/mindsdb/api/http/namespaces/file.py#L138
github.com/mindsdb/mindsdb/security/advisories/GHSA-j8w6-2r9h-cxhj
securitylab.github.com/advisories/GHSL-2023-182_GHSL-2023-184_mindsdb_mindsdb/