Glances Insecure Pickle Deserialization Arbitrary Code Execution (CVE-2024-46607)

Vulnerability Overview Vulnerability Name: Insecure Pickle Deserialization in Version Cache Leads to Arbitrary Code Execution Vulnerability Description: uses to read a version check cache file, which is stored in a predictable, world-accessible path (such as or ). No integrity checks, signature verification, or format validation are performed before deserialization. An attacker can implant a malicious pickle file into this path (via any reasonable local or container-level scenario) and achieve arbitrary code execution when Glances is run as the OS user during the next version check start (enabled by default). Impact Scope Affected Versions: Fixed Versions: CVSS v3 Base Metrics: - Attack Vector: Local - Attack Complexity: Low - Privileges Required: Low - User Interaction: None - Scope: Unchanged - Confidentiality: High - Integrity: High - Availability: High CVE ID: CVE-2024-46607 Weakness: CWE-502 Credit: sectroyer Remediation Recommended Fix: Replace pickle with JSON for the version cache. The data is a simple Python dictionary containing two string values and one datetime object. JSON representation is very straightforward. Additional Hardening Measures: If pickle is retained, the cache file should be protected using an HMAC key derived from Glances-managed secrets (e.g., a random key stored in the Glances configuration directory). This directory itself should be set to 0600 permissions. Permission Restrictions: As an additional hardening measure, limit the permissions of the Glances cache directory to 0700 upon creation. POC Code Attack Scenario A — Local Privilege Escalation (Shared Multi-User Host) Step 1 — Identify Cache Path Step 2 — Create and Implant Malicious Pickle Step 3 — Wait for Glances to Start (or Restart) Glances automatically calls at startup when (compiled in default). No special configuration by the attacker is required. Step 4 — Verify Execution Attack Scenario B — Container / Shared Volume Poisoning A compromised container sharing a Docker/Podman volume with the Glances container can write to the cache path on the shared volume. Upon the next Glances restart (e.g., rolling update), the payload will execute with privileges inside the Glances container. Attack Scenario C — Symbolic Link Race Condition (TOCTOU) Before the Glances cache directory is initially created (e.g., during a fresh installation), an attacker with write access can create a symbolic link in : When Glances writes its legitimate cache file, it writes to , and the attacker can replace it with a malicious pickle file before the next startup. Minimal Self-Contained Reproduction Impact Vulnerability Type: Insecure Deserialization (CWE-502) Affected Parties: Any Glances system running version checks (enabled by default) in shared environments where lower-privileged processes can write to the Glances user's XDG cache directory, or in containerized deployments using shared volumes. Impact: - Confidentiality: Complete — The attacker can achieve code execution in the context of the Glances process and can read any data accessible to that user. - Integrity: Complete — Files can be modified, persistence mechanisms can be installed, or system state can be altered. - Availability: Complete — The Glances process can be disrupted; if running as root, the system can be compromised. - In many deployments, Glances runs as root (to access hardware performance counters without specific capabilities). Successful exploitation results in complete root code execution without further privilege escalation steps. Responsible Disclosure We are committed to responsible/coordinated disclosure. We will not publish the details of this vulnerability or release exploit code before a fix is released. Please notify us of your timeline within 90 days so we can coordinate. Credit This issue was discovered by Michał Majchrowicz and Marcin Wyczechowski, members of the AFINE team.

Goal Reached Thanks to every supporter — we hit 100%!

Glances Insecure Pickle Deserialization Arbitrary Code Execution (CVE-2024-46607)

More from this source