Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(dependency maintenance): update dependency semantic-release to v19.0.3 [security] #781

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jun 10, 2022

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
semantic-release 19.0.2 -> 19.0.3 age adoption passing confidence

GitHub 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 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:


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

Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, 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 025bb19 to 6cef7d6 Compare June 22, 2022 08:13
@renovate renovate bot changed the title chore(dependency maintenance): update dependency semantic-release to 19.0.3 [security] chore(dependency maintenance): update dependency semantic-release to 19.0.3 [SECURITY] Jun 27, 2022
@renovate renovate bot changed the title chore(dependency maintenance): update dependency semantic-release to 19.0.3 [SECURITY] chore(dependency maintenance): update dependency semantic-release to 19.0.3 [security] Jun 28, 2022
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch 3 times, most recently from 4ae6721 to c746aa5 Compare July 4, 2022 16:05
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch 2 times, most recently from a6d6c28 to b66d1ac Compare August 17, 2022 08:34
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch 2 times, most recently from 2ee1da1 to d076066 Compare September 8, 2022 08:51
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch 2 times, most recently from 3587504 to 9699d16 Compare November 3, 2022 16:26
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 9699d16 to 6976297 Compare November 14, 2022 15:17
@renovate renovate bot changed the title chore(dependency maintenance): update dependency semantic-release to 19.0.3 [security] chore(dependency maintenance): update dependency semantic-release to v19.0.3 [security] Mar 23, 2023
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch 3 times, most recently from f1eb354 to 5428602 Compare February 26, 2024 10:53
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch 2 times, most recently from 882db91 to f6970fd Compare March 28, 2024 06:26
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch 10 times, most recently from c2d556c to 5452467 Compare April 10, 2024 09:33
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch 6 times, most recently from c3ca948 to b14b174 Compare June 4, 2024 11:57
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch 4 times, most recently from 43fed10 to 7e3d84a Compare June 26, 2024 12:43
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch 3 times, most recently from 860df19 to 329c390 Compare July 10, 2024 13:05
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch 8 times, most recently from a896c5a to 84edf3b Compare August 6, 2024 13:21
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch 4 times, most recently from 1df6d40 to 541a2c1 Compare August 23, 2024 10:02
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch 2 times, most recently from b70fd4f to 37f7fb5 Compare September 16, 2024 10:07
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 37f7fb5 to b7002d2 Compare September 25, 2024 15:32
@renovate renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from b7002d2 to e108a36 Compare September 25, 2024 15:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants