Synk Vulnerability SNYK-JS-Y18N-1021887 transitively in @angular/localize · Issue #39743 · angular/angular · GitHub
Skip to content

Synk Vulnerability SNYK-JS-Y18N-1021887 transitively in @angular/localize #39743

Closed

Description

@Ltchoc221

🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑

Please read https://angular.io/guide/security#report-issues on how to disclose security related issues.

🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑🛑

Issue is not directly in angular code, so creating issue as opposed to following the link above.

Problem: @angular/localize v10.2.3 and v9.1.12 both use yargs@15.13.0, which in turn uses y18n@^4.0.0. y18n has the following Prototype Pollution synk vulnerability, with a remediation of upgrading y18n to v5..0.5 or higher.

yargs@16.1.1 upgrades to y18n@^5.0.5. Is it possible to update the 9.x and 10.x lines of @angular/localize to use this higher version of yargs?

Activity

  1. gauravshah27 commented on Nov 18, 2020

    @gauravshah27

    I am hitting the same issue on my angular project. Any solution?

  2. added
    area: i18nIssues related to localization and internationalization
    area: securityIssues related to built-in security features, such as HTML sanitation
    P2The issue is important to a large percentage of users, with a workaround
    on Nov 18, 2020
  3. modified the milestone: Backlog on Nov 18, 2020
  4. petebacondarwin commented on Nov 18, 2020

    @petebacondarwin
    Contributor

    This sounds like a reasonable request. I will put together a PR today.

  5. added a commit that references this issue on Nov 18, 2020
    43e0987
  6. added 2 commits that reference this issue on Nov 18, 2020
    1806d6e
  7. added a commit that references this issue on Nov 19, 2020
    8ab332b
  8. added a commit that references this issue on Nov 19, 2020
    5b38050
  9. angular-automatic-lock-bot commented on Dec 20, 2020

    @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.

  10. locked and limited conversation to collaborators on Dec 20, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

P2The issue is important to a large percentage of users, with a workaroundarea: i18nIssues related to localization and internationalizationarea: securityIssues related to built-in security features, such as HTML sanitationstate: has PR

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions