Repository navigation
Replies: 1 comment
|
Hey, a CVE was requested 6 days ago, it's just taking them some time. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hi, thanks for publishing GHSA-r225-jhr6-68cc (unauthenticated login, unbounded memory consumption) after my report. It still shows "No known CVE". If you already requested one, there is nothing more to do, since GitHub's CVE queue has been taking several weeks lately. If not, requesting one needs admin rights on the advisory, so it has to come from a maintainer (there is a "Request CVE" option on the advisory page, or
gh api -X POST repos/glanceapp/glance/security-advisories/GHSA-r225-jhr6-68cc/cveif that is easier). Would you be willing to request one when you have a moment? Happy to help if GitHub's team has questions.All reactions