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.

Sign up for GitHub

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

Jump to bottom

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

Open

renovate wants to merge 1 commit into master from renovate/npm-semantic-release-vulnerability

Contributor

renovate bot commented Nov 18, 2020 •

edited

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
semantic-release	`17.2.1` -> `19.0.3`

GitHub Vulnerability Alerts

CVE-2020-26226

Impact

Secrets that would normally be masked by semantic-release can be accidentally disclosed if they contain characters that become encoded when included in a URL.

Patches

Fixed in v17.2.3

Workarounds

Secrets that do not contain characters that become encoded when included in a URL are already masked properly.

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:

Open a discussion in semantic-release discussions

Release Notes

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

`v19.0.3`

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`

Bug Fixes

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

`v19.0.1`

Bug Fixes

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

`v19.0.0`

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`

Bug Fixes

bump @semantic-release/commit-analyzer to 9.0.2 (#2258) (7f971f3)

`v18.0.0`

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

`v17.4.7`

Bug Fixes

engines: fixed defined node version to account for the higher requirement from the npm plugin (#2088) (ea52e17)

`v17.4.6`

Bug Fixes

marked: reverted upgrade to v3 (#2087) (5edff69)

`v17.4.5`

Bug Fixes

deps: update dependency marked to v3 (6e4beb8)

`v17.4.4`

Bug Fixes

corrected spelling of invalid plugin config error (#1979) (80e1665)

`v17.4.3`

Bug Fixes

bump minimal version of lodash to address CVE-2021-23337 (#1931) (55194c1)

`v17.4.2`

Bug Fixes

deps: update dependency hosted-git-info to v4 (#1838) (44b3344)

`v17.4.1`

Bug Fixes

deps: peer dependecy error with marked-terminal (#1829) (07f12b9)

`v17.4.0`

Features

config: Use cosmiconfig defaults to support .cjs config files (#1815) (3ecc196), closes #1814

`v17.3.9`

Bug Fixes

update link to GitLab CI introduction (#1794) (a9be97b)

`v17.3.8`

Bug Fixes

deps: update dependency marked to v2 (a2eaed0)

`v17.3.7`

Bug Fixes

deps: update dependency get-stream to v6 (#1748) (969e460)

`v17.3.6`

Bug Fixes

deps: update dependency cosmiconfig to v7 (#1742) (cc74a4c)
deps: update dependency execa to v5 (#1745) (8262832)

`v17.3.5`

Bug Fixes

pin initial branch to master (#1740) (32a2c91)

`v17.3.4`

Bug Fixes

deps: update to yargs 16.2.0 (#1739) (d2ec893)

`v17.3.3`

Bug Fixes

add logging for top-level errors (#1736) (9f57b84)

`v17.3.2`

Bug Fixes

normalize ci: false into noCi: true after configs get merged (#1732) thanks @dominykas (21c151f)

`v17.3.1`

Bug Fixes

deps: Require find-versions ^4.0.0 (#1722) (52238cb)

`v17.3.0`

Features

docs: note that publish token is required (#1700) (885d87a)

`v17.2.4`

Bug Fixes

escape uri encoded symbols (#1697) (f8f8fbc)

`v17.2.3`

Bug Fixes

mask secrets when characters get uri encoded (ca90b34)

`v17.2.2`

Bug Fixes

don't parse port as part of the path in repository URLs (#1671) (77a75f0)
use valid git credentials when multiple are provided (#1669) (2bf3771)

Configuration

📅 Schedule: Branch creation - "" (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.

If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from cbe4167 to 1ac5a08 Compare

June 3, 2021 04:12

Contributor Author

renovate bot commented Jun 3, 2021 •

edited

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json


real	0m7.610s
user	0m6.610s
sys	0m0.801s
npm ERR! code EBADPLATFORM
npm ERR! notsup Unsupported platform for fsevents@2.1.3: wanted {"os":"darwin"} (current: {"os":"linux","arch":"x64"})
npm ERR! notsup Valid OS:    darwin
npm ERR! notsup Valid Arch:  undefined
npm ERR! notsup Actual OS:   linux
npm ERR! notsup Actual Arch: x64

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate-cache/others/npm/_logs/2022-06-18T13_35_41_157Z-debug-0.log


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

00a90a4

renovate bot force-pushed the renovate/npm-semantic-release-vulnerability branch from 1ac5a08 to 00a90a4 Compare

June 18, 2022 13:36

renovate bot changed the title ~~chore(deps): update dependency semantic-release to v17.2.3 [security]~~ chore(deps): update dependency semantic-release to v19 [security]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment