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 applicationsLearn about Deserialization of Untrusted Data vulnerabilities in an interactive lesson.
Start learningUpgrade graphitedb to version 0.2 or higher.
graphitedb is an A clean, embedded graph database engine for Python.
Affected versions of this package are vulnerable to Deserialization of Untrusted Data in the pickle process. An attacker can execute arbitrary code by providing a specially crafted database file to be loaded by the engine. This is only exploitable if database files from untrusted or third-party sources are loaded.
This vulnerability can be mitigated by avoiding loading database files from untrusted or unknown sources and by migrating existing pickle-based databases to the new JSON format using the provided migration module.
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.