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

High Severity - npm audit security issue: Arbitrary File Overwrite #44

Open
JayeshThamke opened this issue May 8, 2019 · 1 comment

Comments

@JayeshThamke
Copy link

npm module hippie installed v0.5.2 returned npm audit security vulnerability threat on npm install.

I did not find tar dependency inside hippie module in the project. Is there any solution on this vulnerability? Thanks

Following is npm audit report.
=== npm audit security report ===
Manual Review
Some vulnerabilities require your attention to resolve
Visit https://go.npm.me/audit-guide for additional guidance
High Arbitrary File Overwrite
Package tar
Patched in >=4.4.2
Dependency of hippie [dev]
Path hippie > npm > libcipm > npm-lifecycle > node-gyp > tar
More info https://npmjs.com/advisories/803
High Arbitrary File Overwrite
Package tar
Patched in >=4.4.2
Dependency of hippie [dev]
Path hippie > npm > libnpm > npm-lifecycle > node-gyp > tar
More info https://npmjs.com/advisories/803
High Arbitrary File Overwrite
Package tar
Patched in >=4.4.2
Dependency of hippie [dev]
Path hippie > npm > node-gyp > tar
More info https://npmjs.com/advisories/803
High Arbitrary File Overwrite
Package tar
Patched in >=4.4.2
Dependency of hippie [dev]
Path hippie > npm > npm-lifecycle > node-gyp > tar
More info https://npmjs.com/advisories/803
found 4 high severity vulnerabilities in 13578 scanned packages
4 vulnerabilities require manual review. See the full report for details.

@iilei
Copy link

iilei commented May 24, 2019

workaround;
npm audit fix
helped in my case.

tar is a dependency due to

└─┬ hippie@0.5.2
  └─┬ npm@6.9.0
    └─┬ node-gyp@3.8.0
      └─┬ tar@2.2.2
        └── block-stream@0.0.9 

So it seems the latest npm is causing this vulnerability

edit: I filed an issue at npm

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

2 participants