You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
npm-plugin: upgraded to the beta, which upgrades npm to v8 (f634b8c)
upgrade marked to resolve ReDos vulnerability (#2330) (d9e5bc0)
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.
This is a maintenance release. An increasing amount of dependencies required a node version higher than the Node 10 version supported by semantic-release@17. We decided to go straight to a recent Node LTS version because the release build is usually independent of others, requiring a higher node version is less disruptive to users, but helps us reduce the maintenance overhead.
renovateBot
changed the title
chore(deps): update dependency semantic-release to v23 [security]
chore(deps): update dependency semantic-release to v19 [security]
Mar 5, 2024
renovateBot
changed the title
chore(deps): update dependency semantic-release to v19 [security]
chore(deps): update dependency semantic-release to v23 [security]
Mar 14, 2024
renovateBot
changed the title
chore(deps): update dependency semantic-release to v23 [security]
chore(deps): update dependency semantic-release to v19 [security]
Mar 16, 2024
renovateBot
changed the title
chore(deps): update dependency semantic-release to v19 [security]
chore(deps): update dependency semantic-release to v23 [security]
Mar 22, 2024
renovateBot
changed the title
chore(deps): update dependency semantic-release to v23 [security]
chore(deps): update dependency semantic-release to v19 [security]
Mar 23, 2024
renovateBot
changed the title
chore(deps): update dependency semantic-release to v19 [security]
chore(deps): update dependency semantic-release to v23 [security]
Mar 24, 2024
renovateBot
changed the title
chore(deps): update dependency semantic-release to v23 [security]
chore(deps): update dependency semantic-release to v19 [security]
Mar 25, 2024
renovateBot
changed the title
chore(deps): update dependency semantic-release to v19 [security]
chore(deps): update dependency semantic-release to v23 [security]
May 2, 2024
renovateBot
changed the title
chore(deps): update dependency semantic-release to v23 [security]
chore(deps): update dependency semantic-release to v19 [security]
May 3, 2024
renovateBot
changed the title
chore(deps): update dependency semantic-release to v24 [security]
chore(deps): update dependency semantic-release to v19 [security]
Jun 6, 2024
renovateBot
changed the title
chore(deps): update dependency semantic-release to v19 [security]
chore(deps): update dependency semantic-release to v24 [security]
Jun 28, 2024
renovateBot
changed the title
chore(deps): update dependency semantic-release to v24 [security]
chore(deps): update dependency semantic-release to v19 [security]
Jun 29, 2024
renovateBot
changed the title
chore(deps): update dependency semantic-release to v19 [security]
chore(deps): update dependency semantic-release to v24 [security]
Oct 10, 2024
renovateBot
changed the title
chore(deps): update dependency semantic-release to v24 [security]
chore(deps): update dependency semantic-release to v19 [security]
Oct 11, 2024
renovateBot
changed the title
chore(deps): update dependency semantic-release to v19 [security]
chore(deps): update dependency semantic-release to v24 [security]
Oct 29, 2024
renovateBot
changed the title
chore(deps): update dependency semantic-release to v24 [security]
chore(deps): update dependency semantic-release to v19 [security]
Oct 31, 2024
renovateBot
changed the title
chore(deps): update dependency semantic-release to v19 [security]
chore(deps): update dependency semantic-release to v24 [security]
Dec 3, 2024
renovateBot
changed the title
chore(deps): update dependency semantic-release to v24 [security]
chore(deps): update dependency semantic-release to v19 [security]
Dec 5, 2024
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^17.0.4→^19.0.3Exposure of Sensitive Information to an Unauthorized Actor in semantic-release
CVE-2022-31051 / GHSA-x2pg-mjhr-2m5x
More information
Details
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:
Severity
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:NReferences
This data is provided by the GitHub Advisory Database (CC-BY 4.0).
Release Notes
semantic-release/semantic-release (semantic-release)
v19.0.3Compare Source
Bug Fixes
v19.0.2Compare Source
Bug Fixes
v19.0.1Compare Source
Bug Fixes
v19.0.0Compare Source
Bug Fixes
markedto resolve ReDos vulnerability (#2330) (d9e5bc0)BREAKING CHANGES
@semantic-release/npmhas also dropped support for node v15markedandmarked-terminalthat 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.v18.0.1Compare Source
Bug Fixes
v18.0.0Compare Source
This is a maintenance release. An increasing amount of dependencies required a node version higher than the Node 10 version supported by
semantic-release@17. We decided to go straight to a recent Node LTS version because the release build is usually independent of others, requiring a higher node version is less disruptive to users, but helps us reduce the maintenance overhead.If you use GitHub Actions and need to bump the node version set up by
actions/node-setup, you can useoctoherd-script-bump-node-version-in-workflowsBREAKING CHANGES
node-version: the minimum required version of node is now v14.17
v17.4.7Compare Source
Bug Fixes
v17.4.6Compare Source
Bug Fixes
v17.4.5Compare Source
Bug Fixes
v17.4.4Compare Source
Bug Fixes
v17.4.3Compare Source
Bug Fixes
CVE-2021-23337(#1931) (55194c1)v17.4.2Compare Source
Bug Fixes
v17.4.1Compare Source
Bug Fixes
marked-terminal(#1829) (07f12b9)v17.4.0Compare Source
Features
v17.3.9Compare Source
Bug Fixes
v17.3.8Compare Source
Bug Fixes
v17.3.7Compare Source
Bug Fixes
v17.3.6Compare Source
Bug Fixes
v17.3.5Compare Source
Bug Fixes
v17.3.4Compare Source
Bug Fixes
v17.3.3Compare Source
Bug Fixes
v17.3.2Compare Source
Bug Fixes
v17.3.1Compare Source
Bug Fixes
v17.3.0Compare Source
Features
v17.2.4Compare Source
Bug Fixes
v17.2.3Compare Source
Bug Fixes
v17.2.2Compare Source
Bug Fixes
v17.2.1Compare Source
Reverts
v17.2.0Compare Source
Features
v17.1.2Compare Source
Bug Fixes
v17.1.1Compare Source
Bug Fixes
v17.1.0Compare Source
Features
v17.0.8Compare Source
Bug Fixes
v17.0.7Compare Source
Bug Fixes
v17.0.6Compare Source
Bug Fixes
v17.0.5Compare Source
Bug Fixes
Configuration
📅 Schedule: (UTC)
🚦 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.