Update introduced version in GHSA advisory (CVE-2025-57752) #6081
Conversation
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
Fixes the issue where security vulnerability is incorrectly applied to projects that depend on the v0.4 version of `next` which is a totally different product than one started at v0.9.9. It was already discussed before, see github#179 for context This problem was already fixed for some previous vulnerabilities of `next`, but constantly gets back, when new vulnerability is introduced Note: I wasn't able to introduce this change via suggest form as it exposes just "Affected versions" field, which logically would have to be `>=0.9.9, < 14.2.31` but that value is not accepted (Looks as another bug worth reporting)
There was a problem hiding this comment.
Pull Request Overview
This PR fixes a security advisory to correctly specify the version range for a CVE affecting the next package. The change prevents false positives for projects using the unrelated v0.4 version of next.
- Updates the
introducedversion field from "0" to "0.9.9" in the GHSA advisory - Aligns the vulnerability scope with the actual affected product versions
- Resolves recurring issue where security advisories incorrectly flag unrelated
nextpackage versions
Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
github-actions
bot
changed the base branch from
main
to
medikoo/advisory-improvement-6081
advisory-database
bot
merged commit e5d43b5
into
github:medikoo/advisory-improvement-6081
2 checks passed
Contributor
|
Hi @medikoo! Thank you so much for contributing to the GitHub Advisory Database. This database is free, open, and accessible to all, and it's people like you who make it great. Thanks for choosing to help others. We hope you send in more contributions in the future! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Fixes the issue where security vulnerability is incorrectly applied to projects that depend on the v0.4 version of
nextwhich is a totally different product than one started at v0.9.9.It was already discussed before, see #179 for context
This problem was already fixed for some previous vulnerabilities of
next, but constantly gets back, when new vulnerability is introducedNote: I wasn't able to introduce this change via suggest form as it exposes just "Affected versions" field, which logically would have to be
>=0.9.9, < 14.2.31but that value is not accepted (Looks as another bug worth reporting)