[GHSA-w5hq-g745-h8pq] uuid: Missing buffer bounds check in v3/v5/v6 when buf is provided#7769
Conversation
|
Hi there @broofa! A community member has suggested an improvement to your security advisory. If approved, this change will affect the global advisory listed at github.com/advisories. It will not affect the version listed in your project repository. This change will be reviewed by our Security Curation Team. If you have thoughts or feedback, please share them in a comment here! If this PR has already been closed, you can start a new community contribution for this advisory |
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 GHSA advisory metadata by refreshing the modified timestamp and expanding the affected packages list to include uuid in the npm ecosystem.
Changes:
- Bumped the advisory
modifiedtimestamp. - Added a new
affectedentry for npm packageuuidwith version range information.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| "fixed": "11.1.1" | ||
| } | ||
| ] | ||
| } | ||
| ], | ||
| "database_specific": { | ||
| "last_known_affected_version_range": "< 3.4.0" | ||
| } |
There was a problem hiding this comment.
Oops this should be updated to <= 3.4.0
|
@VanessaHenderson You're confusing API methods with semver release versions. |
|
ahh that makes a lot more sense @broofa. I know I'm not the only one confused on this from the wording. I'll close this |
Updates
Comments
The CVE + your description explicitly call out the 3x, 5x, 6x range. While there is no published/available versions of UUID 5x and 6x, there is versions of 3x still available for download that are just deprecated.