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(dependencies): update dependency semantic-release to 19.0.3 [security] - autoclosed #240
Closed
Conversation
This file contains 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
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
June 23, 2022 20:52
684982d
to
76b75fd
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
September 25, 2022 16:35
76b75fd
to
d7a42be
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
November 20, 2022 10:55
d7a42be
to
ff64048
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
March 19, 2023 00:07
ff64048
to
d075ca3
Compare
renovate
bot
changed the title
chore(dependencies): update dependency semantic-release to 19.0.3 [security]
chore(dependencies): update dependency semantic-release to 19.0.3 [security] - autoclosed
Mar 24, 2023
renovate
bot
changed the title
chore(dependencies): update dependency semantic-release to 19.0.3 [security] - autoclosed
chore(dependencies): update dependency semantic-release to 19.0.3 [security]
Mar 26, 2023
renovate
bot
changed the title
chore(dependencies): update dependency semantic-release to 19.0.3 [security]
chore(dependencies): update dependency semantic-release to 19.0.3 [security] - autoclosed
Mar 26, 2023
renovate
bot
changed the title
chore(dependencies): update dependency semantic-release to 19.0.3 [security] - autoclosed
chore(dependencies): update dependency semantic-release to 19.0.3 [security]
Mar 27, 2023
renovate
bot
changed the title
chore(dependencies): update dependency semantic-release to 19.0.3 [security]
chore(dependencies): update dependency semantic-release to 19.0.3 [security] - autoclosed
Mar 27, 2023
renovate
bot
changed the title
chore(dependencies): update dependency semantic-release to 19.0.3 [security] - autoclosed
chore(dependencies): update dependency semantic-release to 19.0.3 [security]
Mar 27, 2023
renovate
bot
changed the title
chore(dependencies): update dependency semantic-release to 19.0.3 [security]
chore(dependencies): update dependency semantic-release to 19.0.3 [security] - autoclosed
Mar 27, 2023
renovate
bot
changed the title
chore(dependencies): update dependency semantic-release to 19.0.3 [security] - autoclosed
chore(dependencies): update dependency semantic-release to 19.0.3 [security]
Mar 27, 2023
renovate
bot
changed the title
chore(dependencies): update dependency semantic-release to 19.0.3 [security]
chore(dependencies): update dependency semantic-release to 19.0.3 [security] - autoclosed
Mar 27, 2023
renovate
bot
changed the title
chore(dependencies): update dependency semantic-release to 19.0.3 [security] - autoclosed
chore(dependencies): update dependency semantic-release to 19.0.3 [security]
Mar 31, 2023
renovate
bot
changed the title
chore(dependencies): update dependency semantic-release to 19.0.3 [security]
chore(dependencies): update dependency semantic-release to 19.0.3 [security] - autoclosed
Mar 31, 2023
renovate
bot
changed the title
chore(dependencies): update dependency semantic-release to 19.0.3 [security] - autoclosed
chore(dependencies): update dependency semantic-release to 19.0.3 [security]
Mar 31, 2023
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
April 1, 2023 04:49
dc11a67
to
47f0b21
Compare
renovate
bot
changed the title
chore(dependencies): update dependency semantic-release to 19.0.3 [security]
chore(dependencies): update dependency semantic-release to 19.0.3 [security] - autoclosed
Apr 3, 2023
renovate
bot
changed the title
chore(dependencies): update dependency semantic-release to 19.0.3 [security] - autoclosed
chore(dependencies): update dependency semantic-release to 19.0.3 [security]
Apr 3, 2023
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
April 5, 2023 20:19
47f0b21
to
44e09a9
Compare
renovate
bot
changed the title
chore(dependencies): update dependency semantic-release to 19.0.3 [security]
chore(dependencies): update dependency semantic-release to 19.0.3 [security] - autoclosed
Apr 17, 2023
renovate
bot
changed the title
chore(dependencies): update dependency semantic-release to 19.0.3 [security] - autoclosed
chore(dependencies): update dependency semantic-release to 19.0.3 [security]
Apr 18, 2023
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
April 18, 2023 17:13
44e09a9
to
4ddd523
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
April 27, 2023 19:04
4ddd523
to
d2c8b4b
Compare
renovate
bot
force-pushed
the
renovate/npm-semantic-release-vulnerability
branch
from
May 8, 2023 12:49
d2c8b4b
to
1d22000
Compare
renovate
bot
changed the title
chore(dependencies): update dependency semantic-release to 19.0.3 [security]
chore(dependencies): update dependency semantic-release to 19.0.3 [security] - autoclosed
May 28, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
None yet
0 participants
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.4.4
->19.0.3
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:
Configuration
📅 Schedule: Branch creation - "" in timezone 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 has been generated by Mend Renovate. View repository job log here.