Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Repo specific advisories with CVE IDs don't make it into the global set

Open
#3,266 3 comments 5 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
30/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
github, grafana
Domain
databases, security

Research direction

Start with the Grafana advisory GHSA-2x6g-h2hg-rq84 and compare its assigned CVE-2022-39306 with the GitHub Advisory Database search result. Trace how repo-specific advisories with CVE IDs are handled, and consider the issue resolved when that CVE is present in the global database.

Written by the indexing model from the issue text.

Description

It looks like if a repo has an advisory that was not marked to enter the global database, and that advisory is assigned a CVE ID, the CVE ID in question is not present in the GitHub Advisory Database.

I feel like I'm not explaining this well, so I have an example.

This Grafana advisory
https://github.com/grafana/grafana/security/advisories/GHSA-2x6g-h2hg-rq84

Has been assigned CVE-2022-39306

If you search the GitHub advisory database, that ID doesn't show up.

It is nice to use the GitHub database, even for unreviewed IDs, because it's vastly more complete and accurate for supported ecosystems than other sources. Incomplete CVE data means multiple data sources must be queried to get a full picture of which IDs exist.

Related is https://github.com/github/advisory-database/issues/2963 where I suggest allowing community contributions for non supported ecosystems, it would be a service to the world to have a public place to store useful details uncovered during investigations

Dominant language
No language data
Stars
2.5k
Forks
772
Avg merge
3d 15h
Merged PRs (30d)
46

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from github/advisory-database

All issues in github/advisory-database

Similar issues

More Databases issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.