graphitedb
Affected
- introduced
0, fixed0.2(ecosystem)
Fixed versions
0.2
Fix
- Fixed version
0.2pip install --upgrade graphitedb==0.2
Advisory
Also known as: None
Graphite Has a Pickle Deserialization Vulnerability
Impact
Type of vulnerability: Insecure Deserialization via Python's pickle module.
Who is impacted:
Users of *Graphite graph database engine* versions before 0.2 who load database files from untrusted or third-party sources.
An attacker could craft a malicious database file that executes arbitrary code when loaded by the engine. This is possible because the engine used pickle for serialization, which is known to be unsafe for untrusted data.
Patches
The vulnerability has been patched starting from version 0.2.
All users should upgrade to version 0.2 or later (the current version is 0.4 at publishing time).
In version 0.2 and above, the engine uses JSON instead of pickle for database storage, eliminating the deserialization risk.
Workarounds
If users cannot upgrade immediately:
from graphite.Migration import convert_pickle_to_json
convert_pickle_to_json("path/to/old_database.pkl", "path/to/new_database.json")
After migration, you can safely use the database with version 0.2+.
Note: Versions 0.2 and later will show a warning when attempting to load legacy pickle files, reminding you to migrate them. Also, you can't load pickle files in 0.2 and later.
Resources
graphite.Migration module documentationHigh Basis: The source's own band: HIGH
0, fixed 0.2 (ecosystem)0.2
0.2pip install --upgrade graphitedb==0.2Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0