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(deps): update dependency semver to v7.5.2 [security] #10941

Merged
merged 1 commit into from
Mar 25, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Feb 19, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
semver 7.3.5 -> 7.5.2 age adoption passing confidence

semver vulnerable to Regular Expression Denial of Service

CVE-2022-25883 / GHSA-c2qf-rxjj-qqgw

More information

Details

Versions of the package semver before 7.5.2 on the 7.x branch, before 6.3.1 on the 6.x branch, and all other versions before 5.7.2 are vulnerable to Regular Expression Denial of Service (ReDoS) via the function new Range, when untrusted user data is provided as a range.

Severity

  • CVSS Score: 5.3 / 10 (Medium)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

References

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).


Release Notes

npm/node-semver (semver)

v7.5.2

Compare Source

Bug Fixes

v7.5.1

Compare Source

Bug Fixes

v7.5.0

Compare Source

Features
Bug Fixes

v7.4.0

Compare Source

Features
Bug Fixes
Documentation

v7.3.8

Compare Source

Bug Fixes
Documentation
7.3.7 (2022-04-11)
Bug Fixes
Dependencies
7.3.6 (2022-04-05)
Bug Fixes
Documentation
  • clarify * range behavior (cb1ca1d)
Dependencies

v7.3.7

Compare Source

v7.3.6

Compare Source


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 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 has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/npm-semver-vulnerability branch 3 times, most recently from 9f9a718 to 446bcce Compare February 23, 2024 19:10
@renovate renovate bot force-pushed the renovate/npm-semver-vulnerability branch from 446bcce to abdbfa2 Compare March 4, 2024 08:59
Copy link

openzeppelin-code bot commented Mar 4, 2024

chore(deps): update dependency semver to v7.5.2 [security]

Generated at commit: 4ca14e4460e99a4d506c4c027c4a294f6212e084

🚨 Report Summary

Severity Level Results
Contracts Critical
High
Medium
Low
Note
Total
2
3
0
15
39
59
Dependencies Critical
High
Medium
Low
Note
Total
0
0
0
0
0
0

For more details view the full report in OpenZeppelin Code Inspector

@renovate renovate bot force-pushed the renovate/npm-semver-vulnerability branch 3 times, most recently from 4ca14e4 to 9c28612 Compare March 11, 2024 12:58
Copy link

socket-security bot commented Mar 11, 2024

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package New capabilities Transitives Size Publisher
npm/[email protected] None 0 92.6 kB npm-cli-ops

🚮 Removed packages: npm/[email protected]

View full report↗︎

@renovate renovate bot force-pushed the renovate/npm-semver-vulnerability branch 2 times, most recently from ef40bf3 to 6426626 Compare March 12, 2024 10:12
@renovate renovate bot force-pushed the renovate/npm-semver-vulnerability branch from 6426626 to 2c990b6 Compare March 22, 2024 11:40
Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@renovate renovate bot force-pushed the renovate/npm-semver-vulnerability branch from 2c990b6 to 203a16c Compare March 22, 2024 16:16
@lvpeschke lvpeschke merged commit c43354e into master Mar 25, 2024
24 checks passed
@lvpeschke lvpeschke deleted the renovate/npm-semver-vulnerability branch March 25, 2024 15:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant