Skip to content

chore(deps): bump semantic-release to ^19.0.0 [security]#45

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/npm-semantic-release-vulnerability
Open

chore(deps): bump semantic-release to ^19.0.0 [security]#45
renovate[bot] wants to merge 1 commit intomainfrom
renovate/npm-semantic-release-vulnerability

Conversation

@renovate
Copy link
Copy Markdown

@renovate renovate Bot commented Jun 18, 2022

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
semantic-release ^18.0.0^19.0.0 age adoption passing confidence

Exposure 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 encodeURI when 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 Score: 4.4 / 10 (Medium)
  • Vector String: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N

References

This data is provided by the GitHub Advisory Database (CC-BY 4.0).


Release Notes

semantic-release/semantic-release (semantic-release)

v19.0.3

Compare Source

Bug Fixes
  • log-repo: use the original form of the repo url to remove the need to mask credentials (#​2459) (58a226f), closes #​2449

v19.0.2

Compare Source

Bug Fixes
  • npm-plugin: upgraded to the stable version (0eca144)

v19.0.1

Compare Source

Bug Fixes
  • npm-plugin: upgraded to the latest beta version (8097afb)

v19.0.0

Compare Source

Bug Fixes
  • 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.

v18.0.1

Compare Source

Bug Fixes

Configuration

📅 Schedule: (in timezone UTC)

  • Branch creation
    • ""
  • 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 was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch 2 times, most recently from 702a802 to b0dd74f Compare August 13, 2025 14:44
@renovate renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch from b0dd74f to a596b67 Compare August 19, 2025 13:55
@renovate renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch from a596b67 to 5fd2f9b Compare September 25, 2025 14:14
@renovate renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 5fd2f9b to 4cf478b Compare October 21, 2025 09:42
@renovate renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 4cf478b to ac50221 Compare November 10, 2025 14:02
@renovate renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch from ac50221 to 2d1e7a9 Compare December 31, 2025 15:40
@renovate renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 2d1e7a9 to fbac60c Compare January 19, 2026 15:49
@renovate renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch from fbac60c to bcb9553 Compare February 2, 2026 14:48
@renovate renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch from bcb9553 to 308a1f9 Compare February 12, 2026 10:50
@renovate renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 308a1f9 to e687cb1 Compare March 5, 2026 20:19
@renovate renovate Bot changed the title chore(deps): bump semantic-release to ^19.0.0 [security] chore(deps): bump semantic-release to ^19.0.0 [security] - autoclosed Mar 27, 2026
@renovate renovate Bot closed this Mar 27, 2026
@renovate renovate Bot deleted the renovate/npm-semantic-release-vulnerability branch March 27, 2026 01:23
@renovate renovate Bot changed the title chore(deps): bump semantic-release to ^19.0.0 [security] - autoclosed chore(deps): bump semantic-release to ^19.0.0 [security] Mar 30, 2026
@renovate renovate Bot reopened this Mar 30, 2026
@renovate renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch 2 times, most recently from e687cb1 to 00b262f Compare March 30, 2026 22:19
@renovate renovate Bot changed the title chore(deps): bump semantic-release to ^19.0.0 [security] chore(deps): bump semantic-release to ^19.0.0 [security] - autoclosed Apr 27, 2026
@renovate renovate Bot closed this Apr 27, 2026
@renovate renovate Bot changed the title chore(deps): bump semantic-release to ^19.0.0 [security] - autoclosed chore(deps): bump semantic-release to ^19.0.0 [security] Apr 27, 2026
@renovate renovate Bot reopened this Apr 27, 2026
@renovate renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch 2 times, most recently from 00b262f to f1c7bff Compare April 27, 2026 23:16
@renovate renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch from f1c7bff to a3341f2 Compare April 29, 2026 10:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants