Shamefile has an arbitrary file read via shamefile.yaml in shame next
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| BKDDFS | shamefile | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Bkddfs | Shamefile |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-x6p3-76f2-xxvh | Shamefile has an arbitrary file read via shamefile.yaml in shame next |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.184% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Bkddfs
Bkddfs shamefile |
|
| Vendors & Products |
Bkddfs
Bkddfs shamefile |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Shamefile has an arbitrary file read via shamefile.yaml in shame next | |
| Weaknesses | CWE-22 | |
| References |
|
|
| Metrics |
cvssV3_1
|