Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CVE-2020-12265, There is no fixed version for decompress-tar, how to prove there is no issure for decompress-4.2.1? #98

Open
waltbest2 opened this issue May 16, 2022 · 4 comments

Comments

@waltbest2
Copy link

There is no fixed version for decompress-tar, and how to prove there is no issure for decompress-4.2.1?

@MikeNitsenko
Copy link

@waltbest2 did you find a solution for this?
Thanks!

@jeremymeng
Copy link

any updates/recommendations?

@efojs
Copy link

efojs commented Jun 3, 2024

AWS Inspector reports that decompress-tar is vulnerable (linking to https://nvd.nist.gov/vuln/detail/CVE-2020-12265) — was/is the issue in decompress or in decompress-tar?

upd:
looks like in compress (according to fix), so decompress-tar looks false-positive

@efojs
Copy link

efojs commented Jun 4, 2024

There is no fixed version for decompress-tar

decompress-tar is decompress' dependency, it extracts files, but issue was in paths :

package fails to prevent extraction of files with relative paths, allowing attackers to write to any folder in the system,

(source)


how to prove there is no issure for decompress-4.2.1

There are tests in the PR with fix, didn't dive into them, but checking tests can be the way to start.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants