
PEACH
Un cadre d’isolation des locataires
graphlm --upgrade (since 0.4.0) and the first-run setup wizard graphlm --setup (since 0.5.0) spawn the package installer without setting a working directory, so the installer inherits the caller's current directory. graphlm is normally run from inside the repository it maps, so that directory is often untrusted (for example, a freshly cloned third-party repository).
Several installers read files from their working directory:
python -m pip install --upgrade graphlm): -m puts the current directory first on sys.path, so a pip.py or pip/ package in the repository is imported and executed instead of pip.pipx upgrade / pipx install --force): pipx runs python -m pip internally in the same directory, so the same applies.uv pip install --python <exe> ...): uv reads uv.toml / pyproject.toml from the current directory or any parent, so a repository can redirect the install to an index it controls.tool commands).
A user who runs graphlm --upgrade or graphlm --setup (including the automatic first-run wizard) while inside a malicious repository can therefore execute attacker-controlled code with their own privileges, or install a package from an attacker-chosen index.Fixed in the next release (version 0.7.1). Every installer call now runs with its working directory set to the user's home directory (falling back to the filesystem root), and the pip branches pass python -P so the working directory is never added to sys.path.
Run graphlm --upgrade / graphlm --setup only from a directory you trust, such as your home directory. Do not run them from inside a repository you have not reviewed.
Source: NVD
Évaluation gratuite des vulnérabilités
Évaluez vos pratiques de sécurité cloud dans 9 domaines de sécurité afin d’évaluer votre niveau de risque et d’identifier les lacunes dans vos défenses.
Obtenez une démo personnalisée
"La meilleure expérience utilisateur que j’ai jamais vue, offre une visibilité totale sur les workloads cloud."
"Wiz fournit une interface unique pour voir ce qui se passe dans nos environnements cloud."
"Nous savons que si Wiz identifie quelque chose comme critique, c’est qu’il l’est réellement."