In the npm package semantic-release before version 17.2.3, secrets that would normally be masked by `semantic-release` can be accidentally disclosed if they contain characters that become encoded when included in a URL. Secrets that do not contain characters that become encoded when included in a URL are already masked properly. The issue is fixed in version 17.2.3.
CVE-2020-26226 - High Severity Vulnerability
Automated semver compliant package publishing
Library home page: https://registry.npmjs.org/semantic-release/-/semantic-release-15.13.18.tgz
Path to dependency file: sync-moltin-to-zendesk/package.json
Path to vulnerable library: sync-moltin-to-zendesk/node_modules/semantic-release/package.json
Dependency Hierarchy: - :x: **semantic-release-15.13.18.tgz** (Vulnerable Library)
Found in HEAD commit: 38c70e01660808a1e73f70cf01d1a367390ce8bc
In the npm package semantic-release before version 17.2.3, secrets that would normally be masked by `semantic-release` can be accidentally disclosed if they contain characters that become encoded when included in a URL. Secrets that do not contain characters that become encoded when included in a URL are already masked properly. The issue is fixed in version 17.2.3.
Publish Date: 2020-11-18
URL: CVE-2020-26226
Base Score Metrics: - Exploitability Metrics: - Attack Vector: Network - Attack Complexity: Low - Privileges Required: None - User Interaction: Required - Scope: Unchanged - Impact Metrics: - Confidentiality Impact: High - Integrity Impact: High - Availability Impact: None
For more information on CVSS3 Scores, click here.Type: Upgrade version
Origin: https://github.com/semantic-release/semantic-release/security/advisories/GHSA-r2j6-p67h-q639
Release Date: 2020-11-18
Fix Resolution: 17.2.3
Step up your Open Source Security Game with WhiteSource here