We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Path to dependency file: /script/vsts/package.json
Path to vulnerable library: /script/node_modules/yargs/node_modules/yargs-parser/package.json,/script/vsts/node_modules/yargs-parser/package.json
**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation
the bare-bones internationalization library used by yargs
Library home page: https://registry.npmjs.org/y18n/-/y18n-3.2.1.tgz
Path to dependency file: /script/package.json
Path to vulnerable library: /script/node_modules/y18n/package.json
Dependency Hierarchy:
Found in base branch: electron-upgrade
The package y18n before 3.2.2, 4.0.1 and 5.0.5, is vulnerable to Prototype Pollution.
Publish Date: 2020-11-17
URL: CVE-2020-7774
Base Score Metrics:
Type: Upgrade version
Origin: https://www.npmjs.com/advisories/1654
Release Date: 2020-11-17
Fix Resolution (y18n): 3.2.2
Direct dependency fix Resolution (yargs): 5.0.0-candidate
In order to enable automatic remediation, please create workflow rules
the mighty option parser used by yargs
Library home page: https://registry.npmjs.org/yargs-parser/-/yargs-parser-2.4.1.tgz
yargs-parser could be tricked into adding or modifying properties of Object.prototype using a "proto" payload.
Publish Date: 2020-03-16
URL: CVE-2020-7608
Release Date: 2020-03-16
Fix Resolution (yargs-parser): 5.0.0-security.0
Direct dependency fix Resolution (yargs): 7.0.0
In order to enable automatic remediation for this issue, please create workflow rules
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Vulnerable Library - yargs-4.8.1.tgz
Path to dependency file: /script/vsts/package.json
Path to vulnerable library: /script/node_modules/yargs/node_modules/yargs-parser/package.json,/script/vsts/node_modules/yargs-parser/package.json
Vulnerabilities
**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation
Details
CVE-2020-7774
Vulnerable Library - y18n-3.2.1.tgz
the bare-bones internationalization library used by yargs
Library home page: https://registry.npmjs.org/y18n/-/y18n-3.2.1.tgz
Path to dependency file: /script/package.json
Path to vulnerable library: /script/node_modules/y18n/package.json
Dependency Hierarchy:
Found in base branch: electron-upgrade
Vulnerability Details
The package y18n before 3.2.2, 4.0.1 and 5.0.5, is vulnerable to Prototype Pollution.
Publish Date: 2020-11-17
URL: CVE-2020-7774
CVSS 3 Score Details (9.8)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: https://www.npmjs.com/advisories/1654
Release Date: 2020-11-17
Fix Resolution (y18n): 3.2.2
Direct dependency fix Resolution (yargs): 5.0.0-candidate
In order to enable automatic remediation, please create workflow rules
CVE-2020-7608
Vulnerable Library - yargs-parser-2.4.1.tgz
the mighty option parser used by yargs
Library home page: https://registry.npmjs.org/yargs-parser/-/yargs-parser-2.4.1.tgz
Path to dependency file: /script/package.json
Path to vulnerable library: /script/node_modules/yargs/node_modules/yargs-parser/package.json,/script/vsts/node_modules/yargs-parser/package.json
Dependency Hierarchy:
Found in base branch: electron-upgrade
Vulnerability Details
yargs-parser could be tricked into adding or modifying properties of Object.prototype using a "proto" payload.
Publish Date: 2020-03-16
URL: CVE-2020-7608
CVSS 3 Score Details (5.3)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Release Date: 2020-03-16
Fix Resolution (yargs-parser): 5.0.0-security.0
Direct dependency fix Resolution (yargs): 7.0.0
In order to enable automatic remediation, please create workflow rules
In order to enable automatic remediation for this issue, please create workflow rules
The text was updated successfully, but these errors were encountered: