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.
References
Link | Resource |
---|---|
https://github.com/semantic-release/semantic-release/commit/ca90b34c4a9333438cc4d69faeb43362bb991e5a | Patch Third Party Advisory |
https://github.com/semantic-release/semantic-release/security/advisories/GHSA-r2j6-p67h-q639 | Third Party Advisory |
https://github.com/semantic-release/semantic-release/commit/ca90b34c4a9333438cc4d69faeb43362bb991e5a | Patch Third Party Advisory |
https://github.com/semantic-release/semantic-release/security/advisories/GHSA-r2j6-p67h-q639 | Third Party Advisory |
Configurations
History
21 Nov 2024, 05:19
Type | Values Removed | Values Added |
---|---|---|
References | () https://github.com/semantic-release/semantic-release/commit/ca90b34c4a9333438cc4d69faeb43362bb991e5a - Patch, Third Party Advisory | |
References | () https://github.com/semantic-release/semantic-release/security/advisories/GHSA-r2j6-p67h-q639 - Third Party Advisory |
Information
Published : 2020-11-18 22:15
Updated : 2024-11-21 05:19
NVD link : CVE-2020-26226
Mitre link : CVE-2020-26226
CVE.ORG link : CVE-2020-26226
JSON object : View
Products Affected
semantic-release_project
- semantic-release
CWE
CWE-116
Improper Encoding or Escaping of Output