PYSEC-2024-78
Vulnerability from pysec - Published: 2024-09-12 13:15 - Updated: 2024-09-16 19:20An arbitrary code execution vulnerability exists in versions 23.12.4.0 up to 24.7.4.1 of the MindsDB platform, when the ChromaDB integration is installed on the server. If a specially crafted ‘INSERT’ query containing Python code is run against a database created with the ChromaDB engine, the code will be passed to an eval function and executed on the server.
| Name | purl | mindsdb | pkg:pypi/mindsdb |
|---|
{
"affected": [
{
"package": {
"ecosystem": "PyPI",
"name": "mindsdb",
"purl": "pkg:pypi/mindsdb"
},
"ranges": [
{
"events": [
{
"introduced": "23.12.4.0"
},
{
"fixed": "24.7.4.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"23.12.4.0",
"23.12.4.1",
"23.12.4.2",
"24.1.4.0",
"24.2.3.0",
"24.3.4.0",
"24.3.4.1",
"24.3.4.2",
"24.3.5.0",
"24.4.2.0",
"24.4.2.1",
"24.4.3.0",
"24.5.4.0",
"24.6.1.0",
"24.6.1.1",
"24.6.2.0",
"24.6.2.2",
"24.6.3.0",
"24.6.3.1",
"24.6.4.1",
"24.7.1.0",
"24.7.2.0",
"24.7.3.0",
"24.7.4.0"
]
}
],
"aliases": [
"CVE-2024-45848",
"GHSA-9gq6-6936-885w"
],
"details": "An arbitrary code execution vulnerability exists in versions 23.12.4.0 up to 24.7.4.1 of the MindsDB platform, when the ChromaDB integration is installed on the server. If a specially crafted \u2018INSERT\u2019 query containing Python code is run against a database created with the ChromaDB engine, the code will be passed to an eval function and executed on the server.",
"id": "PYSEC-2024-78",
"modified": "2024-09-16T19:20:04.697678+00:00",
"published": "2024-09-12T13:15:00+00:00",
"references": [
{
"type": "EVIDENCE",
"url": "https://hiddenlayer.com/sai-security-advisory/2024-09-mindsdb/"
},
{
"type": "ADVISORY",
"url": "https://hiddenlayer.com/sai-security-advisory/2024-09-mindsdb/"
},
{
"type": "ADVISORY",
"url": "https://github.com/advisories/GHSA-9gq6-6936-885w"
}
],
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.