Browse / Unsafe Model Loading and Supply Chain / Unsafe deserialisation
Unsafe deserialisation
77 records in Unsafe Model Loading and Supply Chain.
- Deserialization of Untrusted Data in Hugging Face Transformers Opening a crafted model file makes the library deserialize attacker-supplied data, which runs code as the current user.
- Deserialization of Untrusted Data in Hugging Face Transformers A malicious model configuration file is deserialized without validation by the MobileViTV2 loader, so opening it runs attacker code in the victim's context.
- Deserialization of Untrusted Data in Hugging Face Transformers Loading a crafted MaskFormer model file makes Transformers deserialise attacker-supplied data unsafely, running code as the user who opened it.
- LangChain pickle deserialization of untrusted data A FAISS index loaded from bytes is deserialised with pickle, so attacker-supplied data executes system commands during loading.
- MindsDB Deserialization of Untrusted Data vulnerability A crafted inhouse model file is deserialised when a describe query touches it, so the embedded payload runs on the server.
- MindsDB Deserialization of Untrusted Data vulnerability A malicious uploaded model is deserialised when it is interacted with, so its embedded payload executes on the server.
- MindsDB Deserialization of Untrusted Data vulnerability A crafted in-house model file uploaded to MindsDB is deserialised during fine-tuning, letting its embedded code run on the server.
- MindsDB Deserialization of Untrusted Data vulnerability A maliciously uploaded inhouse model file runs code on the server when it is loaded to serve a prediction.
- H2O vulnerable to Deserialization of Untrusted Data A crafted Iced model file can embed Java objects, and the loader deserialises any class, so gadget chains run code on import.
- ntlk unsafe deserialization vulnerability Data packages fetched by the NLTK downloader contain pickled Python objects that execute attacker code when loaded from untrusted sources.
- MLFlow unsafe deserialization A malicious scikit-learn model uploaded to MLflow deserialises into code execution when a user loads and interacts with it.
- MLFlow unsafe deserialization A malicious scikit-learn model uploaded to MLflow is deserialised with pickle, so attacker code runs when the model is loaded or used.
- MLFlow unsafe deserialization A malicious serialised scikit-learn or LightGBM model uploaded to MLflow executes code when a user loads and interacts with it.
- MLFlow unsafe deserialization A maliciously crafted MLflow recipe is deserialised unsafely, so loading and running it executes attacker code.
- MLFlow unsafe deserialization A malicious LangChain AgentExecutor model uploaded to MLflow is deserialised when used, executing attacker-chosen code on the consumer's machine.
- MLFlow unsafe deserialization A malicious PyFunc model artifact is deserialised when loaded, so its embedded code runs on the machine that uses the model.
- MLFlow unsafe deserialization Loading a maliciously crafted TensorFlow model through MLflow triggers unsafe deserialisation that runs attacker code on the user's system.
- MLFlow unsafe deserialization A maliciously uploaded PyTorch model in MLflow is deserialised on load, running attacker-chosen code on the machine that interacts with it.
- MLFlow unsafe deserialization A malicious pmdarima model uploaded to MLflow runs arbitrary code on the machine that loads and uses it.
- Skops unsafe deserialization Loading a maliciously crafted skops model file deserialises untrusted data, which runs attacker code on the machine that loads it.
- sagemaker-python-sdk vulnerable to Deserialization of Untrusted Data NumpyDeserializer unpickles object arrays from untrusted input, so a crafted pickle payload can execute code on the client.
- Allegro AI ClearML vulnerable to deserialization of untrusted data The client SDK deserialises artifacts without safety checks, so a maliciously uploaded artifact runs code when an end user interacts with it.
- transformers has a Deserialization of Untrusted Data vulnerability Transformers releases before 4.36 deserialise untrusted data without adequate safeguards, so loading a crafted model artifact can create attacker-chosen objects.
- transformers has a Deserialization of Untrusted Data vulnerability Untrusted serialised data is deserialised in transformers releases before 4.36.0, so a crafted input can trigger unsafe object loading.
- scikit-learn Deserialization of Untrusted Data Loading a crafted joblib model file runs attacker-chosen commands embedded through a reduce method during unpickling.
- pytorch-lightning is vulnerable to Deserialization of Untrusted Data Untrusted data is deserialised unsafely by pytorch-lightning, so a crafted file can trigger attacker-controlled behaviour.
- Arbitrary code execution due to YAML deserialization Keras model_from_yaml calls an unsafe YAML loader, so a crafted model config can instantiate Python objects and run code when loaded.