Overview 223 matches · 1 in Waratek scope · 0 protected · 3 exploited · 2 CISA KEV · 8 public PoC · 5 EPSS ≥ 0.5
223matches
1in Waratek scope0.4%
0protected0.0%
3exploited1.3%
2CISA KEV0.9%
8public PoC3.6%
5EPSS ≥ 0.52.2%
Protected by Waratek
0
0.0%
Rule in development
0
0.0%
Mitigation candidate
1
0.4%
No exploit published
0
0.0%
Outside Waratek scope
3
1.3%
Not applicable
219
98.2%
Withdrawn CVE
0
0.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
223
100.0%
not established
0
0.0%
unrecorded
0
0.0%
split by
peak 63 / year
20141
Not applicable1
Medium1
not blocked1
No public exploit1
20150
20164
Not applicable4
High4
not blocked4
No public exploit4
20178
Not applicable8
Critical3
High3
Medium2
not blocked8
No public exploit8
201811
Not applicable11
High11
not blocked11
Proof of concept only2
Forecast only2
No public exploit7
20199
Not applicable9
Critical2
High4
Medium3
not blocked9
No public exploit9
202016
Not applicable16
Critical4
High9
Medium3
not blocked16
Exploited1
Working exploit published1
No public exploit14
202120
Outside Waratek scope1
Not applicable19
Critical2
High12
Medium6
not blocked20
Proof of concept only2
No public exploit18
202237
Outside Waratek scope1
Not applicable36
Critical1
High29
Medium6
Low1
not blocked37
No public exploit37
202337
Mitigation candidate1
Outside Waratek scope1
Not applicable35
Critical6
High19
Medium12
not blocked37
Exploited2
Proof of concept only1
No public exploit34
20242
Not applicable2
Critical1
Medium1
not blocked2
Proof of concept only1
No public exploit1
202515
Not applicable15
High6
Medium9
not blocked15
No public exploit15
202663
Not applicable63
Critical11
High28
Medium22
Low2
not blocked63
No public exploit63
2014201620182020202220242026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2018-16874 | High | 2018-12-14 | Not applicable | No public exploit | 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 package which contains curly braces (both '{' and '}' characters). Specifically, it is only vulnerable in GOPATH mode, but not in module mode (the distinction is documented at https://golang.org/cmd/go/#hdr-Module_aware_go_get). The attacker can cause an arbitrary filesystem write, which can lead to code execution. |
| CVE-2018-16873 | High | 2018-12-14 | Not applicable | Forecast only | 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 a malicious Go package, or a package that imports it directly or indirectly. Specifically, it is only vulnerable in GOPATH mode, but not in module mode (the distinction is documented at https://golang.org/cmd/go/#hdr-Module_aware_go_get). Using custom domains, it's possible to arrange things so that a Git repository is cloned to a folder named ".git" by using a vanity import path that ends with "/.git". If the Git repository root contains a "HEAD" file, a "config" file, an "objects" directory, a "refs" directory, with some work to ensure the proper ordering of operations, "go get -u" can be tricked into considering the parent directory as a repository root, and running Git commands on it. That will use the "config" file in the original Git repository root for its configuration, and if that config file contains malicious commands, they will execute on the system running "go get -u". |
| CVE-2018-17848 | High | 2018-10-01 | Not applicable | No public exploit | The html package (aka x/net/html) through 2018-09-25 in Go mishandles <math><template><mn><b></template>, leading to a "panic: runtime error" (index out of range) in (*insertionModeStack).pop in node.go, called from inHeadIM, during an html.Parse call. |
| CVE-2018-17847 | High | 2018-10-01 | Not applicable | No public exploit | The html package (aka x/net/html) through 2018-09-25 in Go mishandles <svg><template><desc><t><svg></template>, leading to a "panic: runtime error" (index out of range) in (*nodeStack).pop in node.go, called from (*parser).clearActiveFormattingElements, during an html.Parse call. |
| CVE-2018-17846 | High | 2018-10-01 | Not applicable | No public exploit | The html package (aka x/net/html) through 2018-09-25 in Go mishandles <table><math><select><mi><select></table>, leading to an infinite loop during an html.Parse call because inSelectIM and inSelectInTableIM do not comply with a specification. |
| CVE-2018-17143 | High | 2018-09-17 | Not applicable | No public exploit | The html package (aka x/net/html) through 2018-09-17 in Go mishandles <template><tBody><isindex/action=0>, leading to a "panic: runtime error" in inBodyIM in parse.go during an html.Parse call. |
| CVE-2018-17142 | High | 2018-09-17 | Not applicable | No public exploit | The html package (aka x/net/html) through 2018-09-17 in Go mishandles <math><template><mo><template>, leading to a "panic: runtime error" in parseCurrentToken in parse.go during an html.Parse call. |
| CVE-2018-17075 | High | 2018-09-16 | Not applicable | No public exploit | The html package (aka x/net/html) before 2018-07-13 in Go mishandles "in frameset" insertion mode, leading to a "panic: runtime error" for html.Parse of <template><object>, <template><applet>, or <template><marquee>. This is related to HTMLTreeBuilder.cpp in WebKit. |
| CVE-2018-7187 | High | 2018-02-16 | Not applicable | Forecast only | 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 "://" anywhere in the string), which allows remote attackers to execute arbitrary OS commands via a crafted web site. |
| CVE-2018-6574 | High | 2018-02-07 | Not applicable | Proof of concept only | 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 leveraging the gcc or clang plugin feature, because -fplugin= and -plugin= arguments were not blocked. |
| CVE-2015-5740 | Critical | 2017-10-18 | Not applicable | No public exploit | 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 smuggling attacks via a request with two Content-length headers. |
| CVE-2015-5739 | Critical | 2017-10-18 | Not applicable | No public exploit | The net/http library in net/textproto/reader.go in Go before 1.4.3 does not properly parse HTTP header keys, which allows remote attackers to conduct HTTP request smuggling attacks via a space instead of a hyphen, as demonstrated by "Content Length" instead of "Content-Length." |
| CVE-2017-15042 | Medium | 2017-10-05 | Not applicable | No public exploit | An unintended cleartext issue exists in Go before 1.8.4 and 1.9.x before 1.9.1. RFC 4954 requires that, during SMTP, the PLAIN auth scheme must only be used on network connections secured with TLS. The original implementation of smtp.PlainAuth in Go 1.0 enforced this requirement, and it was documented to do so. In 2013, upstream issue #5184, this was changed so that the server may decide whether PLAIN is acceptable. The result is that if you set up a man-in-the-middle SMTP server that doesn't advertise STARTTLS and does advertise that PLAIN auth is OK, the smtp.PlainAuth implementation sends the username and password. |
| CVE-2017-15041 | Critical | 2017-10-05 | Not applicable | No public exploit | Go before 1.8.4 and 1.9.x before 1.9.1 allows "go get" remote command execution. Using custom domains, it is possible to arrange things so that example.com/pkg1 points to a Subversion repository but example.com/pkg1/pkg2 points to a Git repository. If the Subversion repository includes a Git checkout in its pkg2 directory and some other work is done to ensure the proper ordering of operations, "go get" can be tricked into reusing this Git checkout for the fetch of code from pkg2. If the Subversion repository's Git checkout has malicious commands in .git/hooks/, they will execute on the system running "go get." |
| CVE-2017-1000098 | High | 2017-10-05 | Not applicable | No public exploit | The net/http package's Request.ParseMultipartForm method starts writing to temporary files once the request body size surpasses the given "maxMemory" limit. It was possible for an attacker to generate a multipart request crafted such that the server ran out of file descriptors. |
| CVE-2017-1000097 | High | 2017-10-05 | Not applicable | No public exploit | On Darwin, user's trust preferences for root certificates were not honored. If the user had a root certificate loaded in their Keychain that was explicitly not trusted, a Go program would still verify a connection using that root certificate. |
| CVE-2017-8932 | Medium | 2017-07-06 | Not applicable | No public exploit | A bug in the standard library ScalarMult implementation of curve P-256 for amd64 architectures in Go before 1.7.6 and 1.8.x before 1.8.2 causes incorrect results to be generated for specific input points. An adaptive attack can be mounted to progressively extract the scalar input to ScalarMult by submitting crafted points and observing failures to the derive correct output. This leads to a full key recovery attack against static ECDH, as used in popular JWT libraries. |
| CVE-2017-3204 | High | 2017-04-04 | Not applicable | No public exploit | The Go SSH library (x/crypto/ssh) by default does not verify host keys, facilitating man-in-the-middle attacks. Default behavior changed in commit e4e2799 to require explicitly registering a hostkey verification mechanism. |
| CVE-2016-5386 | High | 2016-07-19 | Not applicable | No public exploit | 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 from the presence of untrusted client data in the HTTP_PROXY environment variable, which might allow remote attackers to redirect a CGI application's outbound HTTP traffic to an arbitrary proxy server via a crafted Proxy header in an HTTP request, aka an "httpoxy" issue. |
| CVE-2016-3959 | High | 2016-05-23 | Not applicable | No public exploit | 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 might allow remote attackers to cause a denial of service (infinite loop) via a crafted public key to a program that uses HTTPS client certificates or SSH server libraries. |
| CVE-2016-3958 | High | 2016-05-23 | Not applicable | No public exploit | 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 current working directory, related to use of the LoadLibrary function. |
| CVE-2015-8618 | High | 2016-01-27 | Not applicable | No public exploit | 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 for attackers to obtain private RSA keys via unspecified vectors. |
| CVE-2014-7189 | Medium | 2014-10-07 | Not applicable | No public exploit | crpyto/tls in Go 1.1 before 1.3.2, when SessionTicketsDisabled is enabled, allows man-in-the-middle attackers to spoof clients via unspecified vectors. |