Skip to content

chore(deps): update dependency semantic-release to v19 [security] - #30

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

chore(deps): update dependency semantic-release to v19 [security]#30
renovate[bot] wants to merge 1 commit into
masterfrom
renovate/npm-semantic-release-vulnerability

Conversation

@renovate

@renovate renovate Bot commented Jun 10, 2022

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
semantic-release 17.4.719.0.3 age 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

v18.0.0

Compare 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 use octoherd-script-bump-node-version-in-workflows

BREAKING CHANGES

node-version: the minimum required version of node is now v14.17


Configuration

📅 Schedule: (in timezone Asia/Seoul)

  • Branch creation
    • ""
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

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 changed the title chore(deps): update dependency semantic-release to v19.0.3 [security] chore(deps): update dependency semantic-release to 19.0.3 [security] Jun 12, 2022
@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch 2 times, most recently from 56f8047 to 59d8cc7 Compare June 19, 2022 19:03
@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch 2 times, most recently from 51aee90 to 479c0dc Compare June 26, 2022 18:22
@renovate renovate Bot changed the title chore(deps): update dependency semantic-release to 19.0.3 [security] chore(deps): update dependency semantic-release to 19.0.3 [SECURITY] Jun 27, 2022
@renovate renovate Bot changed the title chore(deps): update dependency semantic-release to 19.0.3 [SECURITY] chore(deps): 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 a43d86e to e7349a4 Compare July 10, 2022 18:06
@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch 2 times, most recently from 688a6bd to 4b0fe10 Compare July 24, 2022 17:04
@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch 4 times, most recently from 0fb575e to 0cef816 Compare July 31, 2022 18:02
@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 0cef816 to 91e640a Compare August 7, 2022 18:17
@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 91e640a to 19d2a8e Compare August 21, 2022 18:00
@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 19d2a8e to 745ad29 Compare August 28, 2022 19:03
@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 745ad29 to 89e4283 Compare September 11, 2022 18:33
@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 89e4283 to c293c96 Compare September 18, 2022 19:51
@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch from c293c96 to 51157e3 Compare September 26, 2022 03:16
@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch 3 times, most recently from 397f3ec to 8c9b12e Compare October 16, 2022 18:08
@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch 2 times, most recently from 2302eb2 to cc3f8ea Compare October 23, 2022 21:15
@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch 2 times, most recently from 37a96d8 to 904010f Compare November 6, 2022 18:42
@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch 2 times, most recently from afec16a to 6978559 Compare February 5, 2023 20:14
@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 6978559 to 9801ce5 Compare February 26, 2023 21:33
@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch 2 times, most recently from bc60c6a to 59117fa Compare March 19, 2023 17:43
@renovate renovate Bot changed the title chore(deps): update dependency semantic-release to 19.0.3 [security] chore(deps): update dependency semantic-release to v19 [security] Mar 24, 2023
@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch 2 times, most recently from 6d8c0fe to 0c4a03d Compare April 9, 2023 21:02
@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch 2 times, most recently from c999027 to ea745fe Compare April 23, 2023 20:28
@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch from ea745fe to 73837d7 Compare April 30, 2023 19:34
@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch 2 times, most recently from 1ac64ad to f9270ac Compare May 14, 2023 17:52
@renovate renovate Bot changed the title chore(deps): update dependency semantic-release to v19 [security] chore(deps): update dependency semantic-release to 19.0.3 [security] May 17, 2023
@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch from f9270ac to e11091b Compare May 21, 2023 19:29
@renovate renovate Bot changed the title chore(deps): update dependency semantic-release to 19.0.3 [security] chore(deps): update dependency semantic-release to v19 [security] May 28, 2023
@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch from e11091b to 4c4ddd7 Compare June 4, 2023 18:13
@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 4c4ddd7 to 3c22f17 Compare June 11, 2023 18:50
@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 3c22f17 to ce70c4e Compare July 2, 2023 19:57
@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch 2 times, most recently from 09e4186 to be8931b Compare July 23, 2023 18:33
@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch from be8931b to b8f5034 Compare July 30, 2023 18:27
@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch 6 times, most recently from ddfbd43 to 85c2595 Compare August 13, 2023 18:52
@renovate
renovate Bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 85c2595 to 54c0554 Compare August 20, 2023 01:46
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.

1 participant