Skip to content

Server-Side Request Forgery in mindsdb

Moderate severity GitHub Reviewed Published Dec 11, 2023 in mindsdb/mindsdb • Updated Nov 22, 2024

Package

pip mindsdb (pip)

Affected versions

< 23.11.4.1

Patched versions

23.11.4.1

Description

Impact

The put method in mindsdb/mindsdb/api/http/namespaces/file.py does not validate the user-controlled URL in the source variable and uses it to create arbitrary requests on line 115, which allows Server-side request forgery (SSRF). This issue may lead to Information Disclosure. The SSRF allows for forging arbitrary network requests from the MindsDB server. It can be used to scan nodes in internal networks for open ports that may not be accessible externally, as well as scan for existing files on the internal network. It allows for retrieving files with csv, xls, xlsx, json or parquet extensions, which will be viewable via MindsDB GUI. For any other existing files, it is a blind SSRF.

Patches

Use mindsdb staging branch or v23.11.4.1

References

References

@ZoranPandovski ZoranPandovski published to mindsdb/mindsdb Dec 11, 2023
Published by the National Vulnerability Database Dec 11, 2023
Published to the GitHub Advisory Database Dec 12, 2023
Reviewed Dec 12, 2023
Last updated Nov 22, 2024

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

EPSS score

0.050%
(21st percentile)

Weaknesses

CVE ID

CVE-2023-49795

GHSA ID

GHSA-34mr-6q8x-g9r6

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.