Glances: Insecure Pickle Deserialization in Version Cache Leads to Arbitrary Code Execution
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| nicolargo | glances | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Nicolargo | Glances |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-9837-48hr-q32j | Glances has Insecure Pickle Deserialization in its Version Cache that Leads to Arbitrary Code Execution |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.190% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Nicolargo
Nicolargo glances |
|
| Vendors & Products |
Nicolargo
Nicolargo glances |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Glances is an open-source system cross-platform monitoring tool. Prior to 4.5.5, glances/outdated.py uses pickle.load() to read a version-check cache file stored at a predictable, world-accessible path (~/.cache/glances/glances-version.db or $XDG_CACHE_HOME/glances/glances-version.db). No integrity check, signature verification, or format validation is performed before deserialization. An attacker with write access to that path — through any of several realistic local or container-level scenarios — can plant a malicious pickle file and achieve arbitrary code execution as the OS user running Glances the next time it starts with version checking enabled (the default). This vulnerability is fixed in 4.5.5. | |
| Title | Glances: Insecure Pickle Deserialization in Version Cache Leads to Arbitrary Code Execution | |
| Weaknesses | CWE-502 | |
| References |
| |
| Metrics |
cvssV3_1
|