镜像站点 · 本页由第三方 GitHub 只读镜像提供,非 GitHub 官方站点,不接受任何登录或凭据输入。前往 github.com
Skip to content

NPM Audit Failure = @angular-devkit/build-angular #14138

Closed

Description

@Adam-Kernig

🐞 Bug report

Command (mark with an x)

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

### Is this a regression?
no

### Description
Up to date NG CLI, creating a new project, npm audit strikes


## 🔬 Minimal Reproduction
Up to date NG CLI, creating a new project, npm audit strikes

## 🔥 Exception or Error
<pre><code>
┌──────────────────────────────────────────────────────────────────────────────┐
│                                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                             │
└───────────────┴──────────────────────────────────────────────────────────────┘
</code></pre>


## 🌍 Your Environment
<pre><code>
Angular CLI: 7.3.8
Node: 10.15.0
OS: darwin x64
Angular: 
... 

Package                      Version
------------------------------------------------------
@angular-devkit/architect    0.13.8
@angular-devkit/core         7.3.8
@angular-devkit/schematics   7.3.8
@schematics/angular          7.3.8
@schematics/update           0.13.8
rxjs                         6.3.3
typescript                   3.2.4
</code></pre>

**Anything else relevant?**
Nothing further

Activity

  1. alan-agius4 commented on Apr 11, 2019

    @alan-agius4
    Collaborator

    Hi, thanks for reporting this, however this is caused by an upstream package and will be fixed when they release a new version nodejs/node-gyp#1714

  2. added this to the needsTriage milestone on Apr 11, 2019
  3. spp125 commented on Apr 11, 2019

    @spp125

    I am having the same issue.

  4. cap-akimrey commented on Apr 11, 2019

    @cap-akimrey

    v4.4.8 was just released.

  5. chet-manley commented on Apr 11, 2019

    @chet-manley

    Looks like node-gyp already took care of it.
    nodejs/node-gyp#1713

  6. Adam-Kernig commented on Apr 12, 2019

    @Adam-Kernig
    Author

    Im guessing with it now being resolved we can expect this in the next release?

  7. HansITChange commented on Apr 12, 2019

    @HansITChange

    Building a new app still generates the same error

  8. alan-agius4 commented on Apr 12, 2019

    @alan-agius4
    Collaborator

    node-sass are using an older version of node-gyp. hence we are still blocked on this.

    See: sass/node-sass#2625

  9. ignaciorecuerda commented on Apr 12, 2019

    @ignaciorecuerda

    This question has already been answered. Can you try this solution https://stackoverflow.com/a/55649551/10961281, it has worked for me

  10. Adam-Kernig commented on Apr 12, 2019

    @Adam-Kernig
    Author

    This question has already been answered. Can you try this solution https://stackoverflow.com/a/55649551/10961281, it has worked for me

    Do NOT manually edit the lock file.

  11. Adam-Kernig commented on Apr 12, 2019

    @Adam-Kernig
    Author

    This question has already been answered. Can you try this solution https://stackoverflow.com/a/55649551/10961281, it has worked for me

    Do NOT manually edit the lock file.

    Then how should it be done?

    Wait till sass is updated and give the angular chaps time, it's friday (for us anyway) We aren't releasing this weekend.

    The Angular guys are extremely quick at resolving issues, patience is key.

  12. added a commit that references this issue on Apr 14, 2019
  13. 32 remaining items

  14. alan-agius4 commented on May 16, 2019

    @alan-agius4
    Collaborator

    Closing the issue as this seems to have been fixed upstream without the need to do any changes from our side.

  15. pl4yradam commented on May 16, 2019

    @pl4yradam
  16. franciscojsr commented on May 16, 2019

    @franciscojsr

    Yes! I just did: npm audit fix and solved!

  17. subhashkonda commented on May 16, 2019

    @subhashkonda

    Npm audit fix fixed all issues in my local, but I still see in my CI build showing the tar 2.2.2 high vulnerability. Do you see the issue is still open or is this seems to be my CI Build specific.
    Does anyone facing the same ?

  18. ShahanaFarooqui commented on May 17, 2019

    @ShahanaFarooqui

    @subhashkonda i am also facing the same issue with github. Veulnerability fixed on my local but Github still shows it vulnerable. They might need some more time to update their audit list :).

  19. xaviergxf commented on May 17, 2019

    @xaviergxf

    @alan-agius4 do you know when the dependency will be updated, and a new version of @angular-devkit/build-angular will be released on version 7 (stable)?

  20. salah3x commented on May 17, 2019

    @salah3x

    @xaviergxf, I don't think they need a new release for this issue since it's been fixed upstream.

  21. alan-agius4 commented on May 18, 2019

    @alan-agius4
    Collaborator

    Indeed no release is needed from our side.

  22. unpinned this issue on May 19, 2019
  23. weidenhaus commented on May 27, 2019

    @weidenhaus

    27 May 2019 - Still facing the same issue when creating new Angular project via CLI - 12 high vulnerabilities found.

    The following solved it for me:

    npm i -D node-sass node-pre-gyp node-gyp tar
  24. subhashkonda commented on Jun 6, 2019

    @subhashkonda

    I still have this same issue in CI Builds but in local it is all fine npm audit gives 0 vulnerabilities, So what can be done here???

  25. angular-automatic-lock-bot commented on Sep 9, 2019

    @angular-automatic-lock-bot

    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.

  26. locked and limited conversation to collaborators on Sep 9, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions