NetSight

Security Dashboard

A live picture of new vulnerabilities, flaws exploited in the wild and malicious packages.

Reset
331 matching advisories · page 10 of 12Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
critical9.8 CVE-2020-29511 The encoding/xml package in Go (all versions) does not correctly preserve the semantics of element namespace prefixes during tokenization round-trips, which al… golang · go, netapp · trident 2020-12-14 critical9.8 CVE-2020-29510 The encoding/xml package in Go versions 1.15 and earlier does not correctly preserve the semantics of directives during tokenization round-trips, which allows … golang · go, netapp · trident 2020-12-14 critical9.8 CVE-2020-29509 Authentication Bypass in github.com/russellhaering/gosaml2 go · github.com/russellhaering/gosaml2 2020-12-14 medium5.3 CVE-2020-26265 Go Ethereum, or "Geth", is the official Golang implementation of the Ethereum protocol. go · github.com/ethereum/go-ethereum 2020-12-11 medium6.5 CVE-2020-26264 Go Ethereum, or "Geth", is the official Golang implementation of the Ethereum protocol. go · github.com/ethereum/go-ethereum 2020-12-11 medium6.5 CVE-2020-26242 Go Ethereum, or "Geth", is the official Golang implementation of the Ethereum protocol. go · github.com/ethereum/go-ethereum, go · github.com/holiman/uint256 2020-11-25 medium6.5 CVE-2020-26241 Go Ethereum, or "Geth", is the official Golang implementation of the Ethereum protocol. go · github.com/ethereum/go-ethereum 2020-11-25 medium5.3 CVE-2020-26240 Go Ethereum, or "Geth", is the official Golang implementation of the Ethereum protocol. go · github.com/ethereum/go-ethereum 2020-11-25 high7.5 CVE-2020-28367 Code injection in the go command with cgo before Go 1.14.12 and Go 1.15.5 allows arbitrary code execution at build time via malicious gcc flags specified via a… golang · go 2020-11-18 high7.5 CVE-2020-28366 Code injection in the go command with cgo before Go 1.14.12 and Go 1.15.5 allows arbitrary code execution at build time via a malicious unquoted symbol name in… golang · go, fedoraproject · fedora, netapp · cloud_insights_telegraf_agent +1 2020-11-18 high7.5 CVE-2020-28362 Go before 1.14.12 and 1.15.x before 1.15.4 allows Denial of Service. golang · go, fedoraproject · fedora, netapp · cloud_insights_telegraf_agent +1 2020-11-18 medium6.1 CVE-2020-24553 Go before 1.14.8 and 1.15.x before 1.15.1 allows XSS because text/html is the default for CGI/FCGI handlers that lack a Content-Type header. golang · go, fedoraproject · fedora, opensuse · leap +1 2020-09-02 low2.5 CVE-2020-8912 A vulnerability in the in-band key negotiation exists in the AWS S3 Crypto SDK for GoLang versions prior to V2. go · github.com/aws/aws-sdk-go 2020-08-11 medium5.6 CVE-2020-8911 A padding oracle vulnerability exists in the AWS S3 Crypto SDK for GoLang versions prior to V2. go · github.com/aws/aws-sdk-go 2020-08-11 high7.5 CVE-2020-16845 Withdrawn Advisory: Infinite loop in xz go · github.com/ulikunitz/xz 2020-08-06 medium5.9 CVE-2020-15586 Go before 1.13.13 and 1.14.x before 1.14.5 has a data race in some net/http servers, as demonstrated by the httputil.ReverseProxy Handler, because it reads a r… golang · go, cloudfoundry · cf-deployment, cloudfoundry · routing-release +3 2020-07-17 medium5.3 CVE-2020-14039 In Go before 1.13.13 and 1.14.x before 1.14.5, Certificate.Verify may lack a check on the VerifyOptions.KeyUsages EKU requirements (if VerifyOptions.Roots equa… golang · go, opensuse · leap 2020-07-17 high7.5 CVE-2020-14040 The x/text package before 0.3.3 for Go has a vulnerability in encoding/unicode that could lead to the UTF-16 decoder entering an infinite loop, causing the pro… go · golang.org/x/text 2020-06-17 high7.5 CVE-2019-11939 Golang Facebook Thrift servers would not error upon receiving messages declaring containers of sizes larger than the payload. go · github.com/facebook/fbthrift 2020-03-18 high7.5 CVE-2020-7919 Helm uses crypto package vulnerable to panic from malformed X.509 certificate go · github.com/helm/helm, go · golang.org/x/crypto, go · helm.sh/helm/v3 2020-03-16 high7.5 CVE-2020-9283 golang.org/x/crypto before v0.0.0-20200220183623-bac4c82f6975 for Go allows a panic during signature verification in the golang.org/x/crypto/ssh package. go · golang.org/x/crypto 2020-02-20 critical9.8 CVE-2015-5741 The net/http library in net/http/transfer.go in Go before 1.4.3 does not properly parse HTTP headers, which allows remote attackers to conduct HTTP request smu… golang · go, redhat · openstack, redhat · enterprise_linux 2020-02-08 high7.5 CVE-2019-17596 Go before 1.12.11 and 1.3.x before 1.13.2 can panic upon an attempt to process network traffic containing an invalid DSA public key. golang · go, debian · debian_linux, fedoraproject · fedora +8 2019-10-24 high7.5 CVE-2019-16276 Go before 1.12.10 and 1.13.x before 1.13.1 allow HTTP Request Smuggling. golang · go, debian · debian_linux, opensuse · leap +6 2019-09-30 high7.5 CVE-2019-9514 golang.org/x/net/http vulnerable to a reset flood go · golang.org/x/net 2019-08-13 high7.5 CVE-2019-9512 golang.org/x/net/http vulnerable to ping floods go · golang.org/x/net 2019-08-13 critical9.8 CVE-2019-14809 net/url in Go before 1.11.13 and 1.12.x before 1.12.8 mishandles malformed hosts in URLs, leading to an authorization bypass in some applications. golang · go, debian · debian_linux 2019-08-13 medium5.9 CVE-2019-11841 Golang/x/crypto message forgery vulnerability go · golang.org/x/crypto 2019-05-22 critical9.8 CVE-2019-11888 Go through 1.12.5 on Windows mishandles process creation with a nil environment in conjunction with a non-nil token, which allows attackers to obtain sensitive… golang · go 2019-05-13 medium5.9 CVE-2019-11840 An issue was discovered in the supplementary Go cryptography library, golang.org/x/crypto, before v0.0.0-20190320223903-b7391e95e576. go · golang.org/x/crypto 2019-05-09

Get notifications

Subscribe to new vulnerabilities and early warnings from the last seven days. Pick what matters to your stack and copy the address into any feed reader. More filters appear when you pick a type.

Format:
Open feed

Early warnings are advisories that are published before or without a CVE number, for example malicious packages, advisories with a CVE still pending and reports that are not reviewed yet. Confidence says how well an entry is checked: high, medium or low.

About this dashboard

The dashboard keeps its own index of security advisories and refreshes it every 30 minutes. It merges the national vulnerability database, package advisories, malware reports and the catalog of vulnerabilities that are exploited in the wild into one record per issue. Reports about the same flaw are combined, so nothing is listed twice.

Open any entry for the full record: description, severity vector, affected packages and versions, fixed versions, weakness class, exploitation probability and references.

Sources: the GitHub Advisory Database (reviewed advisories, malware reports and unreviewed reports), the National Vulnerability Database, the CVE Program (cve.org) for brand-new records, the OpenSSF malicious packages list, the CISA catalog of Known Exploited Vulnerabilities and Microsoft's blocklist of malicious VS Code extensions. Every entry names its sources on its detail page.

This product uses the NVD API but is not endorsed or certified by the NVD.

Reading the figures

  • Threat level: a rating computed from three numbers shown next to it: critical advisories in the last 24 hours, vulnerabilities newly confirmed as exploited this week and malware reports this week. It is a quick orientation, not an official warning level.
  • Severity: scores from 9.0 are critical, 7.0 to 8.9 high, 4.0 to 6.9 medium and 0.1 to 3.9 low. Severity describes how bad a flaw is in general. It does not know whether the component is reachable in your environment.
  • Known exploited: exploitation has been observed in real attacks. These are the entries to patch first. Entries with a fix deadline show how many days are left.
  • Early warnings: advisories that appear before or without a CVE number, for example malicious packages, reviewed advisories with a CVE still pending and reports that are not reviewed yet.
  • Priority queue: critical and high advisories of the last 7 days and everything newly exploited, ordered by exploitation status, severity and score.

Questions

Where does the data come from?
From public vulnerability databases, package advisories and the catalog of exploited vulnerabilities. NetSight collects them into its own index every 30 minutes and merges duplicates.
How do I check whether I am affected?
Search for your product or package name, open the record and compare your installed version with the affected and fixed versions. A product name alone does not mean your version is affected.
What does known exploited mean?
Exploitation of this vulnerability has been observed in real attacks. Such entries carry a date they were confirmed and, where one exists, a deadline for applying the fix.
What is an early warning?
An advisory that is published before or without a CVE number, such as a malicious package or a reviewed advisory whose CVE is still pending. They give you a head start, but the details can change.
Is a high severity always more urgent than a low one?
No. Severity measures technical impact in general. Exposure of the affected system, observed exploitation and the exploitation probability matter as much.
Can I follow new advisories automatically?
Yes. Use the notification builder further down to create an RSS, Atom or JSON feed filtered by severity, technology, ecosystem or exploitation status.