fix(GHSA-v98h-vmpc-fpqv): add fixed:5.11.1 to open-ended npm/NuGet/Packagist ranges#8002
Open
bluvulture wants to merge 1 commit into
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
Updates the OSV/GHSA advisory to represent the remediation boundary using explicit fixed events rather than database_specific.last_known_affected_version_range.
Changes:
- Added
"fixed": "5.11.1"to the affected version range events (repeated across affected entries). - Removed
database_specific.last_known_affected_version_rangefrom the affected entries.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Comment on lines
26
to
+35
| "events": [ | ||
| { | ||
| "introduced": "0" | ||
| }, | ||
| { | ||
| "fixed": "5.11.1" | ||
| } | ||
| ] | ||
| } | ||
| ], | ||
| "database_specific": { | ||
| "last_known_affected_version_range": "< 5.11.1" | ||
| } | ||
| ] |
github-actions
Bot
changed the base branch from
main
to
bluvulture/advisory-improvement-8002
|
👋 This pull request has been marked as stale because it has been open with no activity. You can: comment on the issue or remove the stale label to hold stale off for a while, add the |
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.
Problem
The
npm tinymce,NuGet TinyMCE, andPackagist tinymce/tinymceaffected entrieswith
"introduced": "0"are missing a"fixed"event. Without a fixed bound, the OSVecosystem version enumeration populates those entries with all known versions from
the registry — including patched releases like 7.9.3 and 8.5.1.
This causes OSV-Scanner to report
tinymce/tinymce@7.9.3as vulnerable despite itbeing the fix release for this CVE, producing false positives for users who have
already upgraded.
Fix
Added
"fixed": "5.11.1"to the open-ended range events fornpm tinymce,NuGet TinyMCE, andPackagist tinymce/tinymce. This correctly bounds the legacy5.x range and prevents patched versions from appearing in the affected versions list.
The pattern is consistent with how the NuGet entry was already correctly expressed in
GHSA-q742-qvgc-gc2f, which includes
"fixed": "5.11.1"in itsintroduced: 0range.References
related:
#8001
#8000