CVE-2024-47877 — extract
Fix: codeclysm/extract@4a98568CVE-2024-47877 is a Path Traversal vulnerability in github.com/codeclysm/extract/v3. A fix is available for github.com/codeclysm/extract/v3 — see the affected versions and patch details below.
Extract has insufficient checks allowing attacker to create symlinks outside the extraction directory.
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-47877.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
Real-World Exposure
github.com/codeclysm/extract/v3🐹github.com/codeclysm/extract/v4🐹github.com/codeclysm/extractReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Impact
A maliciously crafted archive may allow an attacker to create a symlink outside the extraction target directory.
Patches
Please use version 4.0.0 or later github.com/codeclysm/extract/v4. Any previous version is affected by the bug.
Workarounds
No knows workarounds.
Backward compatibility notes about upgrading to /v4 from /v3
If you're not using the extract.Extractor.FS interface, you will not face any breaking changes and upgrading should be as simple as changing the import to /v4. This should be the case for most of the userbase.
If you're using the Extractor.FS interface, then upgrading to /v4 will require to implement the new methods that have been added:
type FS interface {
Link(string, string) error
MkdirAll(string, os.FileMode) error
OpenFile(name string, flag int, perm os.FileMode) (*os.File, error)
Symlink(string, string) error
// The following methods have been added in the /v4 interface:
Remove(path string) error
Stat(name string) (os.FileInfo, error)
Chmod(name string, mode os.FileMode) error
}
There should be no other breaking changes in the /v4 API.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/codeclysm/extract/v3 | all versions | No fix |
| 🐹Go | github.com/codeclysm/extract/v4 | all versions | 4.0.0go get github.com/codeclysm/extract/v4@v4.0.0 |
| 🐹Go | github.com/codeclysm/extract | all versions | No fix |
Affected Products
extractcodeclysmDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/codeclysm/extract/v3, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
A fix is available for CVE-2024-47877; check the affected-versions list above or the advisory for the patched release of github.com/codeclysm/extract/v3, then make sure no transitive dependency still pins the vulnerable range.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.
Frequently Asked Questions
Is CVE-2024-47877 in your dependencies?
Find it across Go, including transitive dependencies.