You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Each of these advisories is for a different package in the same repository.
However, according to the CVE submitted by GitHub, it appears that these are all treated as crossbeam package issues, which causes issues to be reported in the wrong packages or not reported in packages that should be reported (crossbeam-rs/crossbeam#1151).
Hey @taiki-e 👋
Sorry for the annoyance, that you're dealing with but we (GitHub) don't actually add those cpe values. If you check the history on the nvd pages you'll see that nvd themselves add the cpes. For what its worth they have a contact email listed here https://nvd.nist.gov/products/cpe
which you can ping. Sorry for giving you a run around 😞
I have written three advisories in crossbeam-rs/crossbeam and obtained CVE via GitHub advisory for all of them.
crossbeam-channel
)crossbeam-deque
)crossbeam-utils
)Each of these advisories is for a different package in the same repository.
However, according to the CVE submitted by GitHub, it appears that these are all treated as
crossbeam
package issues, which causes issues to be reported in the wrong packages or not reported in packages that should be reported (crossbeam-rs/crossbeam#1151).The text was updated successfully, but these errors were encountered: