security(deps-tree): update semantic-release to v19 [security]#78
Open
renovate[bot] wants to merge 1 commit into
Open
security(deps-tree): update semantic-release to v19 [security]#78renovate[bot] wants to merge 1 commit into
semantic-release to v19 [security]#78renovate[bot] wants to merge 1 commit into
Conversation
27c763d to
cb0f047
Compare
cb0f047 to
8b21795
Compare
semantic-release to v19 [security]semantic-release [security]
semantic-release [security]semantic-release to v19 [security]
8b21795 to
01dcc53
Compare
01dcc53 to
78d7e99
Compare
semantic-release to v19 [security]semantic-release [security]
semantic-release [security]semantic-release to v19 [security]
78d7e99 to
a98a8c4
Compare
semantic-release to v19 [security]semantic-release [security]
a98a8c4 to
20f7370
Compare
semantic-release [security]semantic-release to v19 [security]
20f7370 to
0ca0494
Compare
semantic-release to v19 [security]semantic-release [security]
0ca0494 to
466b178
Compare
semantic-release [security]semantic-release to v19 [security]
466b178 to
456bb25
Compare
semantic-release to v19 [security]semantic-release [security]
a1f806f to
9229ba1
Compare
semantic-release [security]semantic-release to v19 [security]
semantic-release to v19 [security]semantic-release [security]
9229ba1 to
b6909d6
Compare
semantic-release [security]semantic-release to v19 [security]
b6909d6 to
ab98187
Compare
ab98187 to
e08e6fb
Compare
semantic-release to v19 [security]semantic-release [security]
e7b08f5 to
f27a7c9
Compare
semantic-release [security]semantic-release to v19 [security]
semantic-release to v19 [security]semantic-release [security]
f27a7c9 to
913fc41
Compare
semantic-release [security]semantic-release to v19 [security]
913fc41 to
79b9458
Compare
semantic-release to v19 [security]semantic-release [security]
79b9458 to
1db4339
Compare
semantic-release [security]semantic-release to v19 [security]
1db4339 to
68f49df
Compare
semantic-release to v19 [security]semantic-release [security]
68f49df to
b2ec7db
Compare
semantic-release [security]semantic-release to v19 [security]
b2ec7db to
110c9ae
Compare
semantic-release to v19 [security]semantic-release [security]
110c9ae to
ce2e7d3
Compare
semantic-release [security]semantic-release to v19 [security]
b686bf8 to
3a7a7ba
Compare
semantic-release to v19 [security]semantic-release [security]
semantic-release [security]semantic-release to v19 [security]
3a7a7ba to
074fb58
Compare
074fb58 to
7004eb3
Compare
semantic-release to v19 [security]semantic-release [security]
semantic-release [security]semantic-release to v19 [security]
7004eb3 to
432de17
Compare
semantic-release to v19 [security]semantic-release [security]
432de17 to
968f0d1
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
^18.0.1→^19.0.0^18.0→^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.Configuration
📅 Schedule: (in timezone Asia/Jakarta)
🚦 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 these updates again.
This PR was generated by Mend Renovate. View the repository job log.