Go helps developers detect, assess, and resolve errors or weaknesses that are at risk of being exploited by attackers. Behind the scenes, the Go team runs a pipeline to curate reports about vulnerabilities, which are stored in the Go vulnerability database. Various libraries and tools can read and analyze those reports to understand how specific user projects may be affected. This functionality is integrated into the Go package discovery site and a new CLI tool, govulncheck.
This project is a work in progress and under active development. We welcome your feedback to help us improve!
NOTE: To report a vulnerability in the Go project, please see the Go Security Policy.
Vulnerability management in Go consists of the following high-level pieces:
The Go vulnerability database contains information from many existing sources in addition to direct reports by Go package maintainers to the Go security team. Each entry in the database is reviewed to ensure that the vulnerability’s description, package and symbol information, and version details are accurate.
Go’s vulnerability detection package, vulncheck, aims to provide a low-noise, reliable way for Go users to learn about known vulnerabilities that may affect their projects. Vulnerability checking is integrated into Go's tools and services, including a new command line tool, govulncheck, the Go package discovery site, and soon, VS Code Go.
To start using govulncheck, run the following from your project:
$ go install golang.org/x/vuln/cmd/govulncheck@latest $ govulncheck ./...
We would love for you to contribute and help us make improvements in the following ways:
How do I report a vulnerability in the Go project?
How do I add a public vulnerability to the Go vulnerability database?
To request addition of a public vulnerability to the Go vulnerability database, fill out this form.
A vulnerability is considered public if it has already been disclosed publicly, or if it exists in a package you maintain (and you are ready to disclose it). The form is only for public vulnerabilities in importable Go packages that are not maintained by the Go Team (anything outside the Go standard library, Go toolchain, and golang.org modules).
The form can also be used to request a new CVE ID. Read more here about the Go CVE Numbering Authority.
How do I suggest an edit to a vulnerability?
To suggest an edit to an existing report in the Go vulnerability database, fill out the form here.
How do I report an issue or give feedback about govulncheck?
Submit your issue or feedback on the Go issue tracker.
I found this vulnerability in another database. Why is it not in the Go vulnerability database?
Reports may be excluded from the Go vulnerability database for various reasons, including the relevant vulnerability not being present in a Go package, the vulnerability being in an installable command instead of an importable package, or the vulnerability being subsumed by another vulnerability that is already present in the database. You can learn more about the Go Security team’s reasons for excluding reports here. If you think that a report was incorrectly excluded from vuln.go.dev, please let us know.
Why does the Go vulnerability database not use severity labels?
Most vulnerability reporting formats use severity labels such as “LOW,” “MEDIUM”, and “CRITICAL” to indicate the impact of different vulnerabilities and to help developers prioritize security issues. For several reasons, however, Go avoids using such labels.
The impact of a vulnerability is rarely universal, which means that severity indicators can often be deceptive. For example, a crash in a parser may be a critical severity issue if it is used to parse user-supplied input and can be leveraged in a DoS attack, but if the parser is used to parse local configuration files, even calling the severity “low” might be an overstatement.
Labeling severity is also necessarily subjective. This is true even for the CVE program, which posits a formula to break down relevant aspects of a vulnerability, such as attack vector, complexity, and exploitability. All of these, however, require subjective evaluation.
We believe good descriptions of vulnerabilities are more useful than severity indicators. A good description can break down what an issue is, how it can be triggered, and what consumers should consider when determining the impact on their own software.
Feel free to file an issue if you would like to share your thoughts with us on this topic.