docs/content/github/managing-security-vulnerabilities/browsing-security-vulnerabilities-in-the-github-advisory-database.md

title, intro, versions

title	intro	versions
Browsing security vulnerabilities in the GitHub Advisory Database	The {% data variables.product.prodname_advisory_database %} allows you to browse or search for vulnerabilities that affect open source projects on {% data variables.product.company_short %}.	free-pro-team *

About security vulnerabilities

{% data reusables.repositories.a-vulnerability-is %}

{% data variables.product.product_name %} will send you {% data variables.product.prodname_dependabot_alerts %} if we detect that any of the vulnerabilities from the {% data variables.product.prodname_advisory_database %} affect the packages that your repository depends on. For more information, see "About alerts for vulnerable dependencies."

About the {% data variables.product.prodname_advisory_database %}

The {% data variables.product.prodname_advisory_database %} contains a curated list of security vulnerabilities that have been mapped to packages tracked by the {% data variables.product.company_short %} dependency graph. {% data reusables.repositories.tracks-vulnerabilities %}

Each security advisory contains information about the vulnerability, including the description, severity, affected package, package ecosystem, affected versions and patched versions, impact, and optional information such as references, workarounds, and credits. In addition, advisories from the National Vulnerability Database list contain a link to the CVE record, where you can read more details about the vulnerability, its CVSS scores, and its qualitative severity level. For more information, see the "National Vulnerability Database" from the National Institute of Standards and Technology.

The severity level is one of four possible levels defined in the Common Vulnerability Scoring System (CVSS), Section 2.1.2:

• Low
• Moderate
• High
• Critical

The {% data variables.product.prodname_advisory_database %} uses CVSS version 3.0 standards and the CVSS levels described above. {% data variables.product.product_name %} doesn't publish CVSS scores.

{% data reusables.repositories.github-security-lab %}

Accessing an advisory in the {% data variables.product.prodname_advisory_database %}

1. Navigate to https://github.com/advisories.
2. Optionally, to filter the list, use any of the drop-down menus.
3. Click on any advisory to view details.

{% note %}

The database is also accessible using the GraphQL API. For more information, see the "security_advisory webhook event."

{% endnote %}

Searching the {% data variables.product.prodname_advisory_database %}

You can search the database, and use qualifiers to narrow your search to advisories created on a certain date, in a specific ecosystem, or in a particular library.

{% data reusables.time_date.date_format %} {% data reusables.time_date.time_format %}

{% data reusables.search.date_gt_lt %}

Qualifier	Example
ecosystem:ECOSYSTEM	ecosystem:npm will show only advisories affecting NPM packages.
severity:LEVEL	severity:high will show only advisories with a high severity level.
affects:LIBRARY	affects:lodash will show only advisories affecting the lodash library.
sort:created-asc	sort:created-asc will sort by the oldest advisories first.
sort:created-desc	sort:created-desc will sort by the newest advisories first.
sort:updated-asc	sort:updated-asc will sort by the least recently updated first.
sort:updated-desc	sort:updated-desc will sort by the most recently updated first.
is:withdrawn	is:withdrawn will show only advisories that have been withdrawn.
created:YYYY-MM-DD	created:2019-10-31 will show only advisories created on this date.
updated:YYYY-MM-DD	updated:2019-10-31 will show only advisories updated on this date.

Further reading

• MITRE's definition of "vulnerability"