NetSight

Security Dashboard

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

Reset
180 matching advisories · page 6 of 6Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
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 high7.5 CVE-2020-16845 Withdrawn Advisory: Infinite loop in xz go · github.com/ulikunitz/xz 2020-08-06 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 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 high4.8 CVE-2017-18367 Improper Input Validation in libseccomp-golang go · github.com/seccomp/libseccomp-golang 2019-04-24 high7.8 CVE-2019-9634 Go through 1.12 on Windows misuses certain LoadLibrary functionality, leading to DLL injection. golang · go 2019-03-08 high8.2 CVE-2019-6486 Go before 1.10.8 and 1.11.x before 1.11.5 mishandles P-521 and P-384 elliptic curves, which allows attackers to cause a denial of service (CPU consumption) or … golang · go, debian · debian_linux, opensuse · leap 2019-01-24 high8.1 CVE-2018-16874 In Go before 1.10.6 and 1.11.x before 1.11.3, the "go get" command is vulnerable to directory traversal when executed with the import path of a malicious Go pa… golang · go, opensuse · backports_sle, opensuse · leap +2 2018-12-14 high8.1 CVE-2018-16873 In Go before 1.10.6 and 1.11.x before 1.11.3, the "go get" command is vulnerable to remote code execution when executed with the -u flag and the import path of… golang · go, opensuse · backports_sle, opensuse · leap +2 2018-12-14 high7.5 CVE-2018-17848 golang.org/x/net/html Improper Validation of Array Index vulnerability go · golang.org/x/net 2018-10-01 high7.5 CVE-2018-17847 golang.org/x/net/html has Improper Restriction of Operations within the Bounds of a Memory Buffer go · golang.org/x/net 2018-10-01 high7.5 CVE-2018-17846 x/net/html Vulnerable to DoS During HTML Parsing go · golang.org/x/net 2018-10-01 high7.5 CVE-2018-17143 golang.org/x/net/html has Improper Restriction of Operations within the Bounds of a Memory Buffer go · golang.org/x/net 2018-09-17 high7.5 CVE-2018-17142 golang.org/x/net/html NULL Pointer Dereference vulnerability go · golang.org/x/net 2018-09-17 high7.5 CVE-2018-17075 golang.org/x/net/html NULL Pointer Dereference vulnerability go · golang.org/x/net 2018-09-16 high8.8 CVE-2018-7187 The "go get" implementation in Go 1.9.4, when the -insecure command-line option is used, does not validate the import path (get/vcs.go only checks for "://" an… golang · go, debian · debian_linux 2018-02-16 high7.8 CVE-2018-6574 Go before 1.8.7, Go 1.9.x before 1.9.4, and Go 1.10 pre-releases before Go 1.10rc2 allow "go get" remote command execution during source code build, by leverag… golang · go, debian · debian_linux, redhat · enterprise_linux_server +3 2018-02-07 high7.5 CVE-2017-1000098 The net/http package's Request.ParseMultipartForm method starts writing to temporary files once the request body size surpasses the given "maxMemory" limit. golang · go 2017-10-05 high7.5 CVE-2017-1000097 On Darwin, user's trust preferences for root certificates were not honored. golang · go 2017-10-05 high8.1 CVE-2017-3204 The Go SSH library (x/crypto/ssh) by default does not verify host keys, facilitating man-in-the-middle attacks. go · golang.org/x/crypto 2017-04-04 high8.1 CVE-2016-5386 The net/http package in Go through 1.6 does not attempt to address RFC 3875 section 4.1.18 namespace conflicts and therefore does not protect CGI applications … fedoraproject · fedora, oracle · linux, redhat · enterprise_linux_server +3 2016-07-19 high7.5 CVE-2016-3959 The Verify function in crypto/dsa/dsa.go in Go before 1.5.4 and 1.6.x before 1.6.1 does not properly check parameters passed to the big integer library, which … opensuse · leap, golang · go, fedoraproject · fedora 2016-05-23 high7.8 CVE-2016-3958 Untrusted search path vulnerability in Go before 1.5.4 and 1.6.x before 1.6.1 on Windows allows local users to gain privileges via a Trojan horse DLL in the cu… golang · go 2016-05-23 high7.5 CVE-2015-8618 The Int.Exp Montgomery code in the math/big library in Go 1.5.x before 1.5.3 mishandles carry propagation and produces incorrect output, which makes it easier … opensuse · leap, golang · go 2016-01-27

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.