GHSA-m7x6-qjjp-2qf8 json
A committed cache.dir config makes Fallow write cache files outside the project
published 4d ago modified 4d ago
Unreviewed: the maintainers' own advisory
Published by the maintainers on their GitHub repository fallow-rs/fallow. GitHub has not reviewed it into the GitHub Advisory Database and no CVE record has reached us yet, so everything here comes from the maintainers alone. Read the full advisory on GitHub.
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
Security advisory published by the maintainers of fallow-rs/fallow for fallow: the maintainers' own advisory, not a reviewed GitHub Advisory Database entry. The full advisory is on GitHub.
Patch / fix
- npm fallow 3.43.0
Is GHSA-m7x6-qjjp-2qf8 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | fallow | <=3.42.0 |
3.43.0 |
Classification
- Weakness
-
- CWE-73 External Control of File Name or Path
References
Sources
- Maintainer advisory GHSA-m7x6-qjjp-2qf8
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of fallow-rs/fallow published their own advisory on GitHub. Its facts and headline are shown here; the description stays on GitHub.