Shamefile has an arbitrary file read via shamefile.yaml in shame next
BKDDFS shamefile
BKDDFS shamefile
|
Shamefile is a linter for undocumented linter warnings. Prior to version 0.1.7, a path traversal vulnerability in `shame next` allows an attacker-controlled `shamefile.yaml` to disclose contents of files outside the repository, one line at a time, to the terminal of a user who runs the command. See patch commit for technical details. The issue is fixed in 0.1.7. Upgrade to either 0.1.7 or later versions to incorporate the patch. As a workaround, do not run `shame next` against untrusted `shamefile.yaml`. Use `shame me --dry-run` for CI validation.
From the CVE record · GitHub_M
Before version 0.1.7, path traversal in `shame next` allows an attacker-controlled `shamefile.yaml` to disclose files outside the repository, one line at a time, in the user's terminal. Exploitation requires a user to run the command against the attacker-controlled file.
Anyone running the PyPI, npm, or crates.io shamefile package before version 0.1.7 should check their installation.