Deserialization of Untrusted Data Affecting mindsdb package, versions [23.10.2.0,]
Threat Intelligence
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk ID SNYK-PYTHON-MINDSDB-7945506
- published 13 Sep 2024
- disclosed 12 Sep 2024
- credit Unknown
Introduced: 12 Sep 2024
CVE-2024-45853 Open this link in a new tabHow to fix?
There is no fixed version for MindsDB.
Overview
MindsDB is a MindsDB server, provides server capabilities to mindsdb native python library
Affected versions of this package are vulnerable to Deserialization of Untrusted Data within the predict method of the ModelWrapperUnsafe class in the mindsdb/integrations/handlers/byom_handler/byom_handler.py file, which will perform pickle.loads on a custom model built via the Build Your Own Model process. An attacker can execute arbitrary code on the server by uploading a malicious 'inhouse' model and using it for prediction.
Note:
This can only occur if the BYOM engine is changed in the config from the default venv to inhouse.
Details
Serialization is a process of converting an object into a sequence of bytes which can be persisted to a disk or database or can be sent through streams. The reverse process of creating object from sequence of bytes is called deserialization. Serialization is commonly used for communication (sharing objects between multiple hosts) and persistence (store the object state in a file or a database). It is an integral part of popular protocols like Remote Method Invocation (RMI), Java Management Extension (JMX), Java Messaging System (JMS), Action Message Format (AMF), Java Server Faces (JSF) ViewState, etc.
Deserialization of untrusted data (CWE-502) is when the application deserializes untrusted data without sufficiently verifying that the resulting data will be valid, thus allowing the attacker to control the state or the flow of the execution.