What kind of vulnerability is it? Who is impacted?
Secrets that would normally be masked by semantic-release can be accidentally disclosed if they contain characters that are excluded from uri encoding by encodeURI. Occurrence is further limited to execution contexts where push access to the related repository is not available without modifying the repository url to inject credentials.
Patches
Has the problem been patched? What versions should users upgrade to?
Fixed in 19.0.3
Workarounds
Is there a way for users to fix or remediate the vulnerability without upgrading?
Secrets that do not contain characters that are excluded from encoding with encodeURI when included in a URL are already masked properly.
References
Are there any links users can visit to find out more?
semantic-release/semantic-release (semantic-release)
### [`v19.0.3`](https://redirect.github.com/semantic-release/semantic-release/releases/tag/v19.0.3)
[Compare Source](https://redirect.github.com/semantic-release/semantic-release/compare/v19.0.2...v19.0.3)
##### Bug Fixes
- **log-repo:** use the original form of the repo url to remove the need to mask credentials ([#2459](https://redirect.github.com/semantic-release/semantic-release/issues/2459)) ([58a226f](https://redirect.github.com/semantic-release/semantic-release/commit/58a226f29c04ee56bbb02cc661f020d568849cad)), closes [#2449](https://redirect.github.com/semantic-release/semantic-release/issues/2449)
### [`v19.0.2`](https://redirect.github.com/semantic-release/semantic-release/releases/tag/v19.0.2)
[Compare Source](https://redirect.github.com/semantic-release/semantic-release/compare/v19.0.1...v19.0.2)
##### Bug Fixes
- **npm-plugin:** upgraded to the stable version ([0eca144](https://redirect.github.com/semantic-release/semantic-release/commit/0eca144bad39bf62aa6d207766985657df4fa588))
### [`v19.0.1`](https://redirect.github.com/semantic-release/semantic-release/releases/tag/v19.0.1)
[Compare Source](https://redirect.github.com/semantic-release/semantic-release/compare/v19.0.0...v19.0.1)
##### Bug Fixes
- **npm-plugin:** upgraded to the latest beta version ([8097afb](https://redirect.github.com/semantic-release/semantic-release/commit/8097afb423cf831c72482246d977551ad1361eec))
### [`v19.0.0`](https://redirect.github.com/semantic-release/semantic-release/releases/tag/v19.0.0)
[Compare Source](https://redirect.github.com/semantic-release/semantic-release/compare/v18.0.1...v19.0.0)
##### Bug Fixes
- **npm-plugin:** upgraded to the beta, which upgrades npm to v8 ([f634b8c](https://redirect.github.com/semantic-release/semantic-release/commit/f634b8c3ca498ab170d12ebea9139d1f287ecab5))
- upgrade `marked` to resolve ReDos vulnerability ([#2330](https://redirect.github.com/semantic-release/semantic-release/issues/2330)) ([d9e5bc0](https://redirect.github.com/semantic-release/semantic-release/commit/d9e5bc06044b3493300e7bc38f80efa528e3f298))
##### BREAKING CHANGES
- **npm-plugin:** `@semantic-release/npm` has also dropped support for node v15
- node v15 has been removed from our defined supported versions of node. this was done to upgrade to compatible versions of `marked` and `marked-terminal` that resolved the ReDoS vulnerability. removal of support of this node version should be low since it was not an LTS version and has been EOL for several months already.
Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
[ ] If you want to rebase/retry this PR, check this box
This PR contains the following updates:
18.0.1->19.0.3GitHub Vulnerability Alerts
CVE-2022-31051
Impact
What kind of vulnerability is it? Who is impacted?
Secrets that would normally be masked by semantic-release can be accidentally disclosed if they contain characters that are excluded from uri encoding by encodeURI. Occurrence is further limited to execution contexts where push access to the related repository is not available without modifying the repository url to inject credentials.
Patches
Has the problem been patched? What versions should users upgrade to?
Fixed in 19.0.3
Workarounds
Is there a way for users to fix or remediate the vulnerability without upgrading?
Secrets that do not contain characters that are excluded from encoding with
encodeURIwhen included in a URL are already masked properly.References
Are there any links users can visit to find out more?
For more information
If you have any questions or comments about this advisory:
Release Notes
semantic-release/semantic-release (semantic-release)
### [`v19.0.3`](https://redirect.github.com/semantic-release/semantic-release/releases/tag/v19.0.3) [Compare Source](https://redirect.github.com/semantic-release/semantic-release/compare/v19.0.2...v19.0.3) ##### Bug Fixes - **log-repo:** use the original form of the repo url to remove the need to mask credentials ([#2459](https://redirect.github.com/semantic-release/semantic-release/issues/2459)) ([58a226f](https://redirect.github.com/semantic-release/semantic-release/commit/58a226f29c04ee56bbb02cc661f020d568849cad)), closes [#2449](https://redirect.github.com/semantic-release/semantic-release/issues/2449) ### [`v19.0.2`](https://redirect.github.com/semantic-release/semantic-release/releases/tag/v19.0.2) [Compare Source](https://redirect.github.com/semantic-release/semantic-release/compare/v19.0.1...v19.0.2) ##### Bug Fixes - **npm-plugin:** upgraded to the stable version ([0eca144](https://redirect.github.com/semantic-release/semantic-release/commit/0eca144bad39bf62aa6d207766985657df4fa588)) ### [`v19.0.1`](https://redirect.github.com/semantic-release/semantic-release/releases/tag/v19.0.1) [Compare Source](https://redirect.github.com/semantic-release/semantic-release/compare/v19.0.0...v19.0.1) ##### Bug Fixes - **npm-plugin:** upgraded to the latest beta version ([8097afb](https://redirect.github.com/semantic-release/semantic-release/commit/8097afb423cf831c72482246d977551ad1361eec)) ### [`v19.0.0`](https://redirect.github.com/semantic-release/semantic-release/releases/tag/v19.0.0) [Compare Source](https://redirect.github.com/semantic-release/semantic-release/compare/v18.0.1...v19.0.0) ##### Bug Fixes - **npm-plugin:** upgraded to the beta, which upgrades npm to v8 ([f634b8c](https://redirect.github.com/semantic-release/semantic-release/commit/f634b8c3ca498ab170d12ebea9139d1f287ecab5)) - upgrade `marked` to resolve ReDos vulnerability ([#2330](https://redirect.github.com/semantic-release/semantic-release/issues/2330)) ([d9e5bc0](https://redirect.github.com/semantic-release/semantic-release/commit/d9e5bc06044b3493300e7bc38f80efa528e3f298)) ##### BREAKING CHANGES - **npm-plugin:** `@semantic-release/npm` has also dropped support for node v15 - node v15 has been removed from our defined supported versions of node. this was done to upgrade to compatible versions of `marked` and `marked-terminal` that resolved the ReDoS vulnerability. removal of support of this node version should be low since it was not an LTS version and has been EOL for several months already.Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.