Path Traversal in build/packages/packages.toml Allows Arbitrary Directory Deletion
Gleam
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Gleam Gleam |
| No fix yet |
| Gleam Gleam |
|
Gleam
| Product | Affected | Fixed in |
|---|---|---|
| Gleam Gleam |
| No fix yet |
| Gleam Gleam |
|
≥ v0.18.0-rc1-erlang-slim · < v1.17.0-erlang-slim| No fix yet |
| Gleam Gleam |
| No fix yet |
Path traversal vulnerability in Gleam's dependency management allows arbitrary directory deletion via malicious build/packages/packages.toml content.
Package keys read from build/packages/packages.toml by LocalPackages::read_from_disc are passed without validation to paths.build_packages_package(), which constructs a filesystem path by joining the project build directory with the attacker-controlled key. The resulting path is then passed to fs::delete_directory (which calls remove_dir_all). No check is performed to ensure the path remains within the intended build/packages/ directory. Both absolute paths and relative traversal sequences (e.g. ../) are accepted as package keys, allowing deletion of arbitrary directories.
An attacker who can cause a victim to run gleam deps download on a project containing a malicious build/packages/packages.toml (e.g. by committing the normally-gitignored file to a repository) can cause arbitrary directories on the victim's system to be recursively deleted.
This issue affects gleam: from 0.18.0-rc1 before 1.17.0.
From the CVE record · EEF
Gleam does not validate package keys in build/packages/packages.toml before using them to construct paths for directory deletion. An attacker who places a malicious file in a project can cause arbitrary directories on a victim's system to be recursively deleted when the victim runs `gleam deps download` on that project.
Anyone running Gleam versions from 0.18.0-rc1 up to, but not including, 1.17.0 should check their installation.