Fallow: A `.*` glob segment let an analyzed repository make Fallow test paths in the parent of the project rootGHSA-h4fr-cmh5-qr62
LOWFix: fallow-rs/fallow#3548GHSA-h4fr-cmh5-qr62 is a low-severity (CVSS 3.3) vulnerability in fallow-cli. A fix is available for fallow-cli — see the affected versions and patch details below.
Real-World Exposure
fallow-cli🦀fallow-config🦀fallow-core📦fallow📦@fallow-cli/fallow-nodeReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.
Description
Impact
Fallow expands some globs from the analyzed repository on disk. Before 3.34.0, a segment such as .*, .? or ..* in such a glob also matched the special .. entry. The glob crate tests .. against a segment that starts with a literal .. Fallow validates plugin glob patterns and refuses absolute paths and .. segments, but these segments passed that validation.
The attacker controls the repository content. The attacker must also be able to read the Fallow output, for example a CI log or a pull request comment. Then the attacker can learn if a file or directory exists in the parent of the project root:
- A plugin
fileExistsdetection pattern such as.*/marker.jsonmade the plugin active whenmarker.jsonexisted in the parent directory. - An external plugin
configPatternsoralwaysUsedpattern could match a config file in the parent directory. When the plugin was active and declaredtoolingDependencies, the tooling detection credited the related dev dependency. An unused dependency finding could then disappear, and--trace-dependencyprinted the outside path. fallow plugin-checkreportedpath_exists: truefor a seeded entry that matched only in the parent directory.
Fallow tested only that these paths exist. It did not read or print the content of a file outside the project root through these globs.
The Jest, Vitest and Rstest project globs had the same .* problem, and the Jest and Vitest ones also read file content. GHSA-jfwm-3p3c-6hx5 describes that case.
Patches
Fixed in 3.34.0. Fallow now rewrites a leading . in a wildcard segment to [.] before it expands the glob on disk. [.] matches the same hidden files and directories inside the project root. The glob crate does not test .. against it.
Workarounds
Run Fallow only on repositories that you trust. Before you run Fallow on another repository, check the detection, configPatterns and alwaysUsed patterns of its plugin files.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🦀crates.io | fallow-cli | all versions | 3.34.0cargo update -p fallow-cli --precise 3.34.0 |
| 🦀crates.io | fallow-config | all versions | 3.34.0cargo update -p fallow-config --precise 3.34.0 |
| 🦀crates.io | fallow-core | all versions | 3.34.0cargo update -p fallow-core --precise 3.34.0 |
| 📦npm | fallow | all versions | 3.34.0npm install fallow@3.34.0 |
| 📦npm | @fallow-cli/fallow-node | all versions | 3.34.0npm install @fallow-cli/fallow-node@3.34.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for fallow-cli, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update fallow-cli to 3.34.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h4fr-cmh5-qr62 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is GHSA-h4fr-cmh5-qr62 in your dependencies?
Find it across crates.io, npm, including transitive dependencies.