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 NPM vulnerability - Arbitrary File Overwrite #14221

Closed
marc-wilson opened this issue Apr 19, 2019 · 7 comments
Closed

High NPM vulnerability - Arbitrary File Overwrite #14221

marc-wilson opened this issue Apr 19, 2019 · 7 comments

Comments

@marc-wilson
Copy link

marc-wilson commented Apr 19, 2019

🐞 Bug report

Command (mark with an x)

- [ ] new
- [x] build
- [ ] serve
- [ ] test
- [ ] e2e
- [ ] generate
- [x] add
- [x] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc

Is this a regression?

Yes, the previous version in which this bug was not present was: ....

Description

│ 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 │ @angular-devkit/build-angular [dev] │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ Path │ @angular-devkit/build-angular > node-sass > node-gyp > tar │
├───────────────┼──────────────────────────────────────────────────────────────┤
│ More info │ https://npmjs.com/advisories/803
└───────────────┴──────────────────────────────────────────────────────────────┘

It looks like there's an npm vulnerability in the current angular build. I believe it may be related to this:

A clear and concise description of the problem...

🔬 Minimal Reproduction

🔥 Exception or Error





🌍 Your Environment





Angular CLI: 7.3.8
Node: 10.15.3
OS: darwin x64
Angular: 7.2.13
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, platform-server, router

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.13.8
@angular-devkit/build-angular     0.13.8
@angular-devkit/build-optimizer   0.13.8
@angular-devkit/build-webpack     0.13.8
@angular-devkit/core              7.3.8
@angular-devkit/schematics        7.3.8
@angular/cdk                      7.3.7
@angular/cli                      7.3.8
@angular/material                 7.3.7
@ngtools/webpack                  7.3.8
@schematics/angular               7.3.8
@schematics/update                0.13.8
rxjs                              6.4.0
typescript                        3.2.4
webpack                           4.29.0


Anything else relevant?

@clydin
Copy link
Member

clydin commented Apr 19, 2019

Duplicate of #14138

@clydin clydin marked this as a duplicate of #14138 Apr 19, 2019
@clydin clydin closed this as completed Apr 19, 2019
@subhashkonda
Copy link

Do we have the fix ready for this, npm audit fix or explicit npm install tar is not helping in this case.

@marc-wilson
Copy link
Author

@subhashkonda this was closed because it's a duplicate. See #14138 for details.

@subhashkonda
Copy link

subhashkonda commented Apr 22, 2019

Thanks @mswilson4040, may I know the ETA for this ? If so that would be great.

@marc-wilson
Copy link
Author

@subhashkonda Please refer to my previous comment. I am not associated with any of these teams, so I do not have an ETA. If you look in that original ticket (referenced in my previous comment), there is some chatter about timelines. You can read those to come to your own conclusion as to what an actual time frame may be.

@dmytro-gokun
Copy link

Looks like the downstream dependency that caused the problem is fixed now. Just did clean "npm install" after removing "/node_modules" and "package-lock.json" and that was it 🔨

@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 9, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants