fallow-cli

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 finding could then disappear, and --trace-dependency printed the outside path.
• fallow plugin-check reported path_exists: true for 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.

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 that analysis reads only inside the project root. A crafted repository could make Fallow read files that the user did not expect. Such a read can happen in CI, or when an agent runs Fallow on a cloned repository. The attacker gets changed findings, not the file content.

Versions 2.68.0 to 3.33.1 read outside files through Jest projects. Version 3.33.1 also read them through Vitest test.projects.

Patches

Fixed in 3.34.0. Fallow now resolves each match with symlinks and .. segments removed. Fallow reads the match only when it is inside the project root. A glob whose literal base is outside the project root does not run. The boundary is the project root, so an in-root entry such as <rootDir>/../packages/* still works, also from the config of a workspace package. Fallow also does not read a script --config path that is a symlink to a file outside the project root.

Workarounds

Run Fallow only on repositories that you trust. Before you run Fallow on another repository, check the projects entries of its jest.config.* and vitest.config.* files.

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 finding could then disappear, and --trace-dependency printed the outside path.
• fallow plugin-check reported path_exists: true for 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.

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 that analysis reads only inside the project root. A crafted repository could make Fallow read files that the user did not expect. Such a read can happen in CI, or when an agent runs Fallow on a cloned repository. The attacker gets changed findings, not the file content.

Versions 2.68.0 to 3.33.1 read outside files through Jest projects. Version 3.33.1 also read them through Vitest test.projects.

Patches

Fixed in 3.34.0. Fallow now resolves each match with symlinks and .. segments removed. Fallow reads the match only when it is inside the project root. A glob whose literal base is outside the project root does not run. The boundary is the project root, so an in-root entry such as <rootDir>/../packages/* still works, also from the config of a workspace package. Fallow also does not read a script --config path that is a symlink to a file outside the project root.

Workarounds

Run Fallow only on repositories that you trust. Before you run Fallow on another repository, check the projects entries of its jest.config.* and vitest.config.* files.

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 finding could then disappear, and --trace-dependency printed the outside path.
• fallow plugin-check reported path_exists: true for 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.

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 that analysis reads only inside the project root. A crafted repository could make Fallow read files that the user did not expect. Such a read can happen in CI, or when an agent runs Fallow on a cloned repository. The attacker gets changed findings, not the file content.

Versions 2.68.0 to 3.33.1 read outside files through Jest projects. Version 3.33.1 also read them through Vitest test.projects.

Patches

Fixed in 3.34.0. Fallow now resolves each match with symlinks and .. segments removed. Fallow reads the match only when it is inside the project root. A glob whose literal base is outside the project root does not run. The boundary is the project root, so an in-root entry such as <rootDir>/../packages/* still works, also from the config of a workspace package. Fallow also does not read a script --config path that is a symlink to a file outside the project root.

Workarounds

Run Fallow only on repositories that you trust. Before you run Fallow on another repository, check the projects entries of its jest.config.* and vitest.config.* files.

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 finding could then disappear, and --trace-dependency printed the outside path.
• fallow plugin-check reported path_exists: true for 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.

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 that analysis reads only inside the project root. A crafted repository could make Fallow read files that the user did not expect. Such a read can happen in CI, or when an agent runs Fallow on a cloned repository. The attacker gets changed findings, not the file content.

Versions 2.68.0 to 3.33.1 read outside files through Jest projects. Version 3.33.1 also read them through Vitest test.projects.

Patches

Fixed in 3.34.0. Fallow now resolves each match with symlinks and .. segments removed. Fallow reads the match only when it is inside the project root. A glob whose literal base is outside the project root does not run. The boundary is the project root, so an in-root entry such as <rootDir>/../packages/* still works, also from the config of a workspace package. Fallow also does not read a script --config path that is a symlink to a file outside the project root.

Workarounds

Run Fallow only on repositories that you trust. Before you run Fallow on another repository, check the projects entries of its jest.config.* and vitest.config.* files.

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 finding could then disappear, and --trace-dependency printed the outside path.
• fallow plugin-check reported path_exists: true for 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.

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 that analysis reads only inside the project root. A crafted repository could make Fallow read files that the user did not expect. Such a read can happen in CI, or when an agent runs Fallow on a cloned repository. The attacker gets changed findings, not the file content.

Versions 2.68.0 to 3.33.1 read outside files through Jest projects. Version 3.33.1 also read them through Vitest test.projects.

Patches

Fixed in 3.34.0. Fallow now resolves each match with symlinks and .. segments removed. Fallow reads the match only when it is inside the project root. A glob whose literal base is outside the project root does not run. The boundary is the project root, so an in-root entry such as <rootDir>/../packages/* still works, also from the config of a workspace package. Fallow also does not read a script --config path that is a symlink to a file outside the project root.

Workarounds

Run Fallow only on repositories that you trust. Before you run Fallow on another repository, check the projects entries of its jest.config.* and vitest.config.* files.

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 finding could then disappear, and --trace-dependency printed the outside path.
• fallow plugin-check reported path_exists: true for 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.

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 that analysis reads only inside the project root. A crafted repository could make Fallow read files that the user did not expect. Such a read can happen in CI, or when an agent runs Fallow on a cloned repository. The attacker gets changed findings, not the file content.

Versions 2.68.0 to 3.33.1 read outside files through Jest projects. Version 3.33.1 also read them through Vitest test.projects.

Patches

Fixed in 3.34.0. Fallow now resolves each match with symlinks and .. segments removed. Fallow reads the match only when it is inside the project root. A glob whose literal base is outside the project root does not run. The boundary is the project root, so an in-root entry such as <rootDir>/../packages/* still works, also from the config of a workspace package. Fallow also does not read a script --config path that is a symlink to a file outside the project root.

Workarounds

Run Fallow only on repositories that you trust. Before you run Fallow on another repository, check the projects entries of its jest.config.* and vitest.config.* files.

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 finding could then disappear, and --trace-dependency printed the outside path.
• fallow plugin-check reported path_exists: true for 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.

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 that analysis reads only inside the project root. A crafted repository could make Fallow read files that the user did not expect. Such a read can happen in CI, or when an agent runs Fallow on a cloned repository. The attacker gets changed findings, not the file content.

Versions 2.68.0 to 3.33.1 read outside files through Jest projects. Version 3.33.1 also read them through Vitest test.projects.

Patches

Fixed in 3.34.0. Fallow now resolves each match with symlinks and .. segments removed. Fallow reads the match only when it is inside the project root. A glob whose literal base is outside the project root does not run. The boundary is the project root, so an in-root entry such as <rootDir>/../packages/* still works, also from the config of a workspace package. Fallow also does not read a script --config path that is a symlink to a file outside the project root.

Workarounds

Run Fallow only on repositories that you trust. Before you run Fallow on another repository, check the projects entries of its jest.config.* and vitest.config.* files.

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 finding could then disappear, and --trace-dependency printed the outside path.
• fallow plugin-check reported path_exists: true for 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.

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 that analysis reads only inside the project root. A crafted repository could make Fallow read files that the user did not expect. Such a read can happen in CI, or when an agent runs Fallow on a cloned repository. The attacker gets changed findings, not the file content.

Versions 2.68.0 to 3.33.1 read outside files through Jest projects. Version 3.33.1 also read them through Vitest test.projects.

Patches

Fixed in 3.34.0. Fallow now resolves each match with symlinks and .. segments removed. Fallow reads the match only when it is inside the project root. A glob whose literal base is outside the project root does not run. The boundary is the project root, so an in-root entry such as <rootDir>/../packages/* still works, also from the config of a workspace package. Fallow also does not read a script --config path that is a symlink to a file outside the project root.

Workarounds

Run Fallow only on repositories that you trust. Before you run Fallow on another repository, check the projects entries of its jest.config.* and vitest.config.* files.

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 finding could then disappear, and --trace-dependency printed the outside path.
• fallow plugin-check reported path_exists: true for 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.

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 that analysis reads only inside the project root. A crafted repository could make Fallow read files that the user did not expect. Such a read can happen in CI, or when an agent runs Fallow on a cloned repository. The attacker gets changed findings, not the file content.

Versions 2.68.0 to 3.33.1 read outside files through Jest projects. Version 3.33.1 also read them through Vitest test.projects.

Patches

Fixed in 3.34.0. Fallow now resolves each match with symlinks and .. segments removed. Fallow reads the match only when it is inside the project root. A glob whose literal base is outside the project root does not run. The boundary is the project root, so an in-root entry such as <rootDir>/../packages/* still works, also from the config of a workspace package. Fallow also does not read a script --config path that is a symlink to a file outside the project root.

Workarounds

Run Fallow only on repositories that you trust. Before you run Fallow on another repository, check the projects entries of its jest.config.* and vitest.config.* files.

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 finding could then disappear, and --trace-dependency printed the outside path.
• fallow plugin-check reported path_exists: true for 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.

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 that analysis reads only inside the project root. A crafted repository could make Fallow read files that the user did not expect. Such a read can happen in CI, or when an agent runs Fallow on a cloned repository. The attacker gets changed findings, not the file content.

Versions 2.68.0 to 3.33.1 read outside files through Jest projects. Version 3.33.1 also read them through Vitest test.projects.

Patches

Fixed in 3.34.0. Fallow now resolves each match with symlinks and .. segments removed. Fallow reads the match only when it is inside the project root. A glob whose literal base is outside the project root does not run. The boundary is the project root, so an in-root entry such as <rootDir>/../packages/* still works, also from the config of a workspace package. Fallow also does not read a script --config path that is a symlink to a file outside the project root.

Workarounds

Run Fallow only on repositories that you trust. Before you run Fallow on another repository, check the projects entries of its jest.config.* and vitest.config.* files.

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 finding could then disappear, and --trace-dependency printed the outside path.
• fallow plugin-check reported path_exists: true for 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.

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 that analysis reads only inside the project root. A crafted repository could make Fallow read files that the user did not expect. Such a read can happen in CI, or when an agent runs Fallow on a cloned repository. The attacker gets changed findings, not the file content.

Versions 2.68.0 to 3.33.1 read outside files through Jest projects. Version 3.33.1 also read them through Vitest test.projects.

Patches

Fixed in 3.34.0. Fallow now resolves each match with symlinks and .. segments removed. Fallow reads the match only when it is inside the project root. A glob whose literal base is outside the project root does not run. The boundary is the project root, so an in-root entry such as <rootDir>/../packages/* still works, also from the config of a workspace package. Fallow also does not read a script --config path that is a symlink to a file outside the project root.

Workarounds

Run Fallow only on repositories that you trust. Before you run Fallow on another repository, check the projects entries of its jest.config.* and vitest.config.* files.

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 finding could then disappear, and --trace-dependency printed the outside path.
• fallow plugin-check reported path_exists: true for 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.

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 that analysis reads only inside the project root. A crafted repository could make Fallow read files that the user did not expect. Such a read can happen in CI, or when an agent runs Fallow on a cloned repository. The attacker gets changed findings, not the file content.

Versions 2.68.0 to 3.33.1 read outside files through Jest projects. Version 3.33.1 also read them through Vitest test.projects.

Patches

Fixed in 3.34.0. Fallow now resolves each match with symlinks and .. segments removed. Fallow reads the match only when it is inside the project root. A glob whose literal base is outside the project root does not run. The boundary is the project root, so an in-root entry such as <rootDir>/../packages/* still works, also from the config of a workspace package. Fallow also does not read a script --config path that is a symlink to a file outside the project root.

Workarounds

Run Fallow only on repositories that you trust. Before you run Fallow on another repository, check the projects entries of its jest.config.* and vitest.config.* files.

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 finding could then disappear, and --trace-dependency printed the outside path.
• fallow plugin-check reported path_exists: true for 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.

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 that analysis reads only inside the project root. A crafted repository could make Fallow read files that the user did not expect. Such a read can happen in CI, or when an agent runs Fallow on a cloned repository. The attacker gets changed findings, not the file content.

Versions 2.68.0 to 3.33.1 read outside files through Jest projects. Version 3.33.1 also read them through Vitest test.projects.

Patches

Fixed in 3.34.0. Fallow now resolves each match with symlinks and .. segments removed. Fallow reads the match only when it is inside the project root. A glob whose literal base is outside the project root does not run. The boundary is the project root, so an in-root entry such as <rootDir>/../packages/* still works, also from the config of a workspace package. Fallow also does not read a script --config path that is a symlink to a file outside the project root.

Workarounds

Run Fallow only on repositories that you trust. Before you run Fallow on another repository, check the projects entries of its jest.config.* and vitest.config.* files.

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 finding could then disappear, and --trace-dependency printed the outside path.
• fallow plugin-check reported path_exists: true for 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.

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 that analysis reads only inside the project root. A crafted repository could make Fallow read files that the user did not expect. Such a read can happen in CI, or when an agent runs Fallow on a cloned repository. The attacker gets changed findings, not the file content.

Versions 2.68.0 to 3.33.1 read outside files through Jest projects. Version 3.33.1 also read them through Vitest test.projects.

Patches

Fixed in 3.34.0. Fallow now resolves each match with symlinks and .. segments removed. Fallow reads the match only when it is inside the project root. A glob whose literal base is outside the project root does not run. The boundary is the project root, so an in-root entry such as <rootDir>/../packages/* still works, also from the config of a workspace package. Fallow also does not read a script --config path that is a symlink to a file outside the project root.

Workarounds

Run Fallow only on repositories that you trust. Before you run Fallow on another repository, check the projects entries of its jest.config.* and vitest.config.* files.

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 finding could then disappear, and --trace-dependency printed the outside path.
• fallow plugin-check reported path_exists: true for 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.

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 that analysis reads only inside the project root. A crafted repository could make Fallow read files that the user did not expect. Such a read can happen in CI, or when an agent runs Fallow on a cloned repository. The attacker gets changed findings, not the file content.

Versions 2.68.0 to 3.33.1 read outside files through Jest projects. Version 3.33.1 also read them through Vitest test.projects.

Patches

Fixed in 3.34.0. Fallow now resolves each match with symlinks and .. segments removed. Fallow reads the match only when it is inside the project root. A glob whose literal base is outside the project root does not run. The boundary is the project root, so an in-root entry such as <rootDir>/../packages/* still works, also from the config of a workspace package. Fallow also does not read a script --config path that is a symlink to a file outside the project root.

Workarounds

Run Fallow only on repositories that you trust. Before you run Fallow on another repository, check the projects entries of its jest.config.* and vitest.config.* files.

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 finding could then disappear, and --trace-dependency printed the outside path.
• fallow plugin-check reported path_exists: true for 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.

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 that analysis reads only inside the project root. A crafted repository could make Fallow read files that the user did not expect. Such a read can happen in CI, or when an agent runs Fallow on a cloned repository. The attacker gets changed findings, not the file content.

Versions 2.68.0 to 3.33.1 read outside files through Jest projects. Version 3.33.1 also read them through Vitest test.projects.

Patches

Fixed in 3.34.0. Fallow now resolves each match with symlinks and .. segments removed. Fallow reads the match only when it is inside the project root. A glob whose literal base is outside the project root does not run. The boundary is the project root, so an in-root entry such as <rootDir>/../packages/* still works, also from the config of a workspace package. Fallow also does not read a script --config path that is a symlink to a file outside the project root.

Workarounds

Run Fallow only on repositories that you trust. Before you run Fallow on another repository, check the projects entries of its jest.config.* and vitest.config.* files.

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 finding could then disappear, and --trace-dependency printed the outside path.
• fallow plugin-check reported path_exists: true for 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.

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 that analysis reads only inside the project root. A crafted repository could make Fallow read files that the user did not expect. Such a read can happen in CI, or when an agent runs Fallow on a cloned repository. The attacker gets changed findings, not the file content.

Versions 2.68.0 to 3.33.1 read outside files through Jest projects. Version 3.33.1 also read them through Vitest test.projects.

Patches

Fixed in 3.34.0. Fallow now resolves each match with symlinks and .. segments removed. Fallow reads the match only when it is inside the project root. A glob whose literal base is outside the project root does not run. The boundary is the project root, so an in-root entry such as <rootDir>/../packages/* still works, also from the config of a workspace package. Fallow also does not read a script --config path that is a symlink to a file outside the project root.

Workarounds

Run Fallow only on repositories that you trust. Before you run Fallow on another repository, check the projects entries of its jest.config.* and vitest.config.* files.

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 finding could then disappear, and --trace-dependency printed the outside path.
• fallow plugin-check reported path_exists: true for 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.

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 that analysis reads only inside the project root. A crafted repository could make Fallow read files that the user did not expect. Such a read can happen in CI, or when an agent runs Fallow on a cloned repository. The attacker gets changed findings, not the file content.

Versions 2.68.0 to 3.33.1 read outside files through Jest projects. Version 3.33.1 also read them through Vitest test.projects.

Patches

Fixed in 3.34.0. Fallow now resolves each match with symlinks and .. segments removed. Fallow reads the match only when it is inside the project root. A glob whose literal base is outside the project root does not run. The boundary is the project root, so an in-root entry such as <rootDir>/../packages/* still works, also from the config of a workspace package. Fallow also does not read a script --config path that is a symlink to a file outside the project root.

Workarounds

Run Fallow only on repositories that you trust. Before you run Fallow on another repository, check the projects entries of its jest.config.* and vitest.config.* files.

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 finding could then disappear, and --trace-dependency printed the outside path.
• fallow plugin-check reported path_exists: true for 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.

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 that analysis reads only inside the project root. A crafted repository could make Fallow read files that the user did not expect. Such a read can happen in CI, or when an agent runs Fallow on a cloned repository. The attacker gets changed findings, not the file content.

Versions 2.68.0 to 3.33.1 read outside files through Jest projects. Version 3.33.1 also read them through Vitest test.projects.

Patches

Fixed in 3.34.0. Fallow now resolves each match with symlinks and .. segments removed. Fallow reads the match only when it is inside the project root. A glob whose literal base is outside the project root does not run. The boundary is the project root, so an in-root entry such as <rootDir>/../packages/* still works, also from the config of a workspace package. Fallow also does not read a script --config path that is a symlink to a file outside the project root.

Workarounds

Run Fallow only on repositories that you trust. Before you run Fallow on another repository, check the projects entries of its jest.config.* and vitest.config.* files.

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 finding could then disappear, and --trace-dependency printed the outside path.
• fallow plugin-check reported path_exists: true for 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.

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 that analysis reads only inside the project root. A crafted repository could make Fallow read files that the user did not expect. Such a read can happen in CI, or when an agent runs Fallow on a cloned repository. The attacker gets changed findings, not the file content.

Versions 2.68.0 to 3.33.1 read outside files through Jest projects. Version 3.33.1 also read them through Vitest test.projects.

Patches

Fixed in 3.34.0. Fallow now resolves each match with symlinks and .. segments removed. Fallow reads the match only when it is inside the project root. A glob whose literal base is outside the project root does not run. The boundary is the project root, so an in-root entry such as <rootDir>/../packages/* still works, also from the config of a workspace package. Fallow also does not read a script --config path that is a symlink to a file outside the project root.

Workarounds

Run Fallow only on repositories that you trust. Before you run Fallow on another repository, check the projects entries of its jest.config.* and vitest.config.* files.

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 finding could then disappear, and --trace-dependency printed the outside path.
• fallow plugin-check reported path_exists: true for 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.

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 that analysis reads only inside the project root. A crafted repository could make Fallow read files that the user did not expect. Such a read can happen in CI, or when an agent runs Fallow on a cloned repository. The attacker gets changed findings, not the file content.

Versions 2.68.0 to 3.33.1 read outside files through Jest projects. Version 3.33.1 also read them through Vitest test.projects.

Patches

Fixed in 3.34.0. Fallow now resolves each match with symlinks and .. segments removed. Fallow reads the match only when it is inside the project root. A glob whose literal base is outside the project root does not run. The boundary is the project root, so an in-root entry such as <rootDir>/../packages/* still works, also from the config of a workspace package. Fallow also does not read a script --config path that is a symlink to a file outside the project root.

Workarounds

Run Fallow only on repositories that you trust. Before you run Fallow on another repository, check the projects entries of its jest.config.* and vitest.config.* files.

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 finding could then disappear, and --trace-dependency printed the outside path.
• fallow plugin-check reported path_exists: true for 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.

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 that analysis reads only inside the project root. A crafted repository could make Fallow read files that the user did not expect. Such a read can happen in CI, or when an agent runs Fallow on a cloned repository. The attacker gets changed findings, not the file content.

Versions 2.68.0 to 3.33.1 read outside files through Jest projects. Version 3.33.1 also read them through Vitest test.projects.

Patches

Fixed in 3.34.0. Fallow now resolves each match with symlinks and .. segments removed. Fallow reads the match only when it is inside the project root. A glob whose literal base is outside the project root does not run. The boundary is the project root, so an in-root entry such as <rootDir>/../packages/* still works, also from the config of a workspace package. Fallow also does not read a script --config path that is a symlink to a file outside the project root.

Workarounds

Run Fallow only on repositories that you trust. Before you run Fallow on another repository, check the projects entries of its jest.config.* and vitest.config.* files.

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 finding could then disappear, and --trace-dependency printed the outside path.
• fallow plugin-check reported path_exists: true for 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.

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 that analysis reads only inside the project root. A crafted repository could make Fallow read files that the user did not expect. Such a read can happen in CI, or when an agent runs Fallow on a cloned repository. The attacker gets changed findings, not the file content.

Versions 2.68.0 to 3.33.1 read outside files through Jest projects. Version 3.33.1 also read them through Vitest test.projects.

Patches

Fixed in 3.34.0. Fallow now resolves each match with symlinks and .. segments removed. Fallow reads the match only when it is inside the project root. A glob whose literal base is outside the project root does not run. The boundary is the project root, so an in-root entry such as <rootDir>/../packages/* still works, also from the config of a workspace package. Fallow also does not read a script --config path that is a symlink to a file outside the project root.

Workarounds

Run Fallow only on repositories that you trust. Before you run Fallow on another repository, check the projects entries of its jest.config.* and vitest.config.* files.

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 finding could then disappear, and --trace-dependency printed the outside path.
• fallow plugin-check reported path_exists: true for 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.

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 that analysis reads only inside the project root. A crafted repository could make Fallow read files that the user did not expect. Such a read can happen in CI, or when an agent runs Fallow on a cloned repository. The attacker gets changed findings, not the file content.

Versions 2.68.0 to 3.33.1 read outside files through Jest projects. Version 3.33.1 also read them through Vitest test.projects.

Patches

Fixed in 3.34.0. Fallow now resolves each match with symlinks and .. segments removed. Fallow reads the match only when it is inside the project root. A glob whose literal base is outside the project root does not run. The boundary is the project root, so an in-root entry such as <rootDir>/../packages/* still works, also from the config of a workspace package. Fallow also does not read a script --config path that is a symlink to a file outside the project root.

Workarounds

Run Fallow only on repositories that you trust. Before you run Fallow on another repository, check the projects entries of its jest.config.* and vitest.config.* files.

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 finding could then disappear, and --trace-dependency printed the outside path.
• fallow plugin-check reported path_exists: true for 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.

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 that analysis reads only inside the project root. A crafted repository could make Fallow read files that the user did not expect. Such a read can happen in CI, or when an agent runs Fallow on a cloned repository. The attacker gets changed findings, not the file content.

Versions 2.68.0 to 3.33.1 read outside files through Jest projects. Version 3.33.1 also read them through Vitest test.projects.

Patches

Fixed in 3.34.0. Fallow now resolves each match with symlinks and .. segments removed. Fallow reads the match only when it is inside the project root. A glob whose literal base is outside the project root does not run. The boundary is the project root, so an in-root entry such as <rootDir>/../packages/* still works, also from the config of a workspace package. Fallow also does not read a script --config path that is a symlink to a file outside the project root.

Workarounds

Run Fallow only on repositories that you trust. Before you run Fallow on another repository, check the projects entries of its jest.config.* and vitest.config.* files.

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 finding could then disappear, and --trace-dependency printed the outside path.
• fallow plugin-check reported path_exists: true for 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.

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 that analysis reads only inside the project root. A crafted repository could make Fallow read files that the user did not expect. Such a read can happen in CI, or when an agent runs Fallow on a cloned repository. The attacker gets changed findings, not the file content.

Versions 2.68.0 to 3.33.1 read outside files through Jest projects. Version 3.33.1 also read them through Vitest test.projects.

Patches

Fixed in 3.34.0. Fallow now resolves each match with symlinks and .. segments removed. Fallow reads the match only when it is inside the project root. A glob whose literal base is outside the project root does not run. The boundary is the project root, so an in-root entry such as <rootDir>/../packages/* still works, also from the config of a workspace package. Fallow also does not read a script --config path that is a symlink to a file outside the project root.

Workarounds

Run Fallow only on repositories that you trust. Before you run Fallow on another repository, check the projects entries of its jest.config.* and vitest.config.* files.

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 finding could then disappear, and --trace-dependency printed the outside path.
• fallow plugin-check reported path_exists: true for 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.

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 that analysis reads only inside the project root. A crafted repository could make Fallow read files that the user did not expect. Such a read can happen in CI, or when an agent runs Fallow on a cloned repository. The attacker gets changed findings, not the file content.

Versions 2.68.0 to 3.33.1 read outside files through Jest projects. Version 3.33.1 also read them through Vitest test.projects.

Patches

Fixed in 3.34.0. Fallow now resolves each match with symlinks and .. segments removed. Fallow reads the match only when it is inside the project root. A glob whose literal base is outside the project root does not run. The boundary is the project root, so an in-root entry such as <rootDir>/../packages/* still works, also from the config of a workspace package. Fallow also does not read a script --config path that is a symlink to a file outside the project root.

Workarounds

Run Fallow only on repositories that you trust. Before you run Fallow on another repository, check the projects entries of its jest.config.* and vitest.config.* files.

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 finding could then disappear, and --trace-dependency printed the outside path.
• fallow plugin-check reported path_exists: true for 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.

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 that analysis reads only inside the project root. A crafted repository could make Fallow read files that the user did not expect. Such a read can happen in CI, or when an agent runs Fallow on a cloned repository. The attacker gets changed findings, not the file content.

Versions 2.68.0 to 3.33.1 read outside files through Jest projects. Version 3.33.1 also read them through Vitest test.projects.

Patches

Fixed in 3.34.0. Fallow now resolves each match with symlinks and .. segments removed. Fallow reads the match only when it is inside the project root. A glob whose literal base is outside the project root does not run. The boundary is the project root, so an in-root entry such as <rootDir>/../packages/* still works, also from the config of a workspace package. Fallow also does not read a script --config path that is a symlink to a file outside the project root.

Workarounds

Run Fallow only on repositories that you trust. Before you run Fallow on another repository, check the projects entries of its jest.config.* and vitest.config.* files.

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 finding could then disappear, and --trace-dependency printed the outside path.
• fallow plugin-check reported path_exists: true for 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.

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 that analysis reads only inside the project root. A crafted repository could make Fallow read files that the user did not expect. Such a read can happen in CI, or when an agent runs Fallow on a cloned repository. The attacker gets changed findings, not the file content.

Versions 2.68.0 to 3.33.1 read outside files through Jest projects. Version 3.33.1 also read them through Vitest test.projects.

Patches

Fixed in 3.34.0. Fallow now resolves each match with symlinks and .. segments removed. Fallow reads the match only when it is inside the project root. A glob whose literal base is outside the project root does not run. The boundary is the project root, so an in-root entry such as <rootDir>/../packages/* still works, also from the config of a workspace package. Fallow also does not read a script --config path that is a symlink to a file outside the project root.

Workarounds

Run Fallow only on repositories that you trust. Before you run Fallow on another repository, check the projects entries of its jest.config.* and vitest.config.* files.

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 finding could then disappear, and --trace-dependency printed the outside path.
• fallow plugin-check reported path_exists: true for 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.

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 that analysis reads only inside the project root. A crafted repository could make Fallow read files that the user did not expect. Such a read can happen in CI, or when an agent runs Fallow on a cloned repository. The attacker gets changed findings, not the file content.

Versions 2.68.0 to 3.33.1 read outside files through Jest projects. Version 3.33.1 also read them through Vitest test.projects.

Patches

Fixed in 3.34.0. Fallow now resolves each match with symlinks and .. segments removed. Fallow reads the match only when it is inside the project root. A glob whose literal base is outside the project root does not run. The boundary is the project root, so an in-root entry such as <rootDir>/../packages/* still works, also from the config of a workspace package. Fallow also does not read a script --config path that is a symlink to a file outside the project root.

Workarounds

Run Fallow only on repositories that you trust. Before you run Fallow on another repository, check the projects entries of its jest.config.* and vitest.config.* files.

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 finding could then disappear, and --trace-dependency printed the outside path.
• fallow plugin-check reported path_exists: true for 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.

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 that analysis reads only inside the project root. A crafted repository could make Fallow read files that the user did not expect. Such a read can happen in CI, or when an agent runs Fallow on a cloned repository. The attacker gets changed findings, not the file content.

Versions 2.68.0 to 3.33.1 read outside files through Jest projects. Version 3.33.1 also read them through Vitest test.projects.

Patches

Fixed in 3.34.0. Fallow now resolves each match with symlinks and .. segments removed. Fallow reads the match only when it is inside the project root. A glob whose literal base is outside the project root does not run. The boundary is the project root, so an in-root entry such as <rootDir>/../packages/* still works, also from the config of a workspace package. Fallow also does not read a script --config path that is a symlink to a file outside the project root.

Workarounds

Run Fallow only on repositories that you trust. Before you run Fallow on another repository, check the projects entries of its jest.config.* and vitest.config.* files.

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 finding could then disappear, and --trace-dependency printed the outside path.
• fallow plugin-check reported path_exists: true for 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.

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 that analysis reads only inside the project root. A crafted repository could make Fallow read files that the user did not expect. Such a read can happen in CI, or when an agent runs Fallow on a cloned repository. The attacker gets changed findings, not the file content.