Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.
Open advisories
2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.
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 fileExists detection pattern such as ./marker.json made the plugin active when marker.json existed in the parent directory. - An external plugin configPatterns or alwaysUsed pattern could match a config file in the parent directory. When the plugin was active and declared toolingDependencies, the tooling detection credited the related dev dependency. An unused dependency…
Recommended action: Upgrade to 3.34.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Impact Fallow reads the Jest and Vitest configs of the repository that it analyzes. A Jest projects entry or a Vitest test.projects entry can name a path. Fallow followed such an entry to a config file and read that file, also when the file was outside the project root. These forms reached outside the root: - an absolute path or glob, for example /etc/; - a path with .. segments, for example ../; - a glob with a . segment, because the glob crate also tests .. against a segment that starts with a literal .; - a symlink in the project root to a directory above it; - the extends path of a Vitest inline project; - a script --config path that is a symlink to a file outside the project root. Fallow parsed each of these files as a test runner config. Fallow used the content only to credit dependencies, setup files and JSX import sources. Thus unused dependency and unused file findings could change. Fallow did not print the content or send it over the network. The Fallow threat model states…
Recommended action: Upgrade to 3.34.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.