Overview 173 matches · 1 in Waratek scope · 0 protected · 2 exploited · 2 CISA KEV · 6 public PoC · 4 EPSS ≥ 0.5
173matches
1in Waratek scope0.6%
0protected0.0%
2exploited1.2%
2CISA KEV1.2%
6public PoC3.5%
4EPSS ≥ 0.52.3%
Protected by Waratek
0
0.0%
Rule in development
0
0.0%
Mitigation candidate
1
0.6%
No exploit published
0
0.0%
Outside Waratek scope
0
0.0%
Not applicable
172
99.4%
Withdrawn CVE
0
0.0%
blocked by ARMR today
0
0.0%
partly blocked
0
0.0%
not blocked
173
100.0%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
2
1.2%
Working exploit published
0
0.0%
Proof of concept only
5
2.9%
Forecast only
2
1.2%
No public exploit
164
94.8%
split by
peak 37 / year
20141
Not applicable1
Medium1
not blocked1
No public exploit1
20150
20164
Not applicable4
High4
not blocked4
No public exploit4
20177
Not applicable7
Critical3
High2
Medium2
not blocked7
No public exploit7
20185
Not applicable5
High5
not blocked5
Proof of concept only2
Forecast only2
No public exploit1
20197
Not applicable7
Critical2
High4
Medium1
not blocked7
No public exploit7
202013
Not applicable13
Critical4
High6
Medium3
not blocked13
Exploited1
No public exploit12
202118
Not applicable18
Critical2
High10
Medium6
not blocked18
Proof of concept only2
No public exploit16
202233
Not applicable33
Critical1
High25
Medium6
Low1
not blocked33
No public exploit33
202332
Mitigation candidate1
Not applicable31
Critical6
High18
Medium8
not blocked32
Exploited1
No public exploit31
20242
Not applicable2
Critical1
Medium1
not blocked2
Proof of concept only1
No public exploit1
202514
Not applicable14
High6
Medium8
not blocked14
No public exploit14
202637
Not applicable37
Critical3
High19
Medium13
Low2
not blocked37
No public exploit37
2014201620182020202220242026
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2022-30629 | Low | 2022-08-10 | Not applicable | No public exploit | Non-random values for ticket_age_add in session tickets in crypto/tls before Go 1.17.11 and Go 1.18.3 allow an attacker that can observe TLS handshakes to correlate successive connections by comparing ticket ages during session resumption. |
| CVE-2022-30580 | High | 2022-08-10 | Not applicable | No public exploit | Code injection in Cmd.Start in os/exec before Go 1.17.11 and Go 1.18.3 allows execution of any binaries in the working directory named either "..com" or "..exe" by calling Cmd.Run, Cmd.Start, Cmd.Output, or Cmd.CombinedOutput when Cmd.Path is unset. |
| CVE-2022-29804 | High | 2022-08-10 | Not applicable | No public exploit | Incorrect conversion of certain invalid paths to valid, absolute paths in Clean in path/filepath before Go 1.17.11 and Go 1.18.3 on Windows allows potential directory traversal attack. |
| CVE-2022-28131 | High | 2022-08-10 | Not applicable | No public exploit | Uncontrolled recursion in Decoder.Skip in encoding/xml before Go 1.17.12 and Go 1.18.4 allows an attacker to cause a panic due to stack exhaustion via a deeply nested XML document. |
| CVE-2022-1962 | Medium | 2022-08-10 | Not applicable | No public exploit | Uncontrolled recursion in the Parse functions in go/parser before Go 1.17.12 and Go 1.18.4 allow an attacker to cause a panic due to stack exhaustion via deeply nested types or declarations. |
| CVE-2022-1705 | Medium | 2022-08-10 | Not applicable | No public exploit | Acceptance of some invalid Transfer-Encoding headers in the HTTP/1 client in net/http before Go 1.17.12 and Go 1.18.4 allows HTTP request smuggling if combined with an intermediate server that also improperly fails to reject the header as invalid. |
| CVE-2022-30634 | High | 2022-07-15 | Not applicable | No public exploit | Infinite loop in Read in crypto/rand before Go 1.17.11 and Go 1.18.3 on Windows allows attacker to cause an indefinite hang by passing a buffer larger than 1 << 32 - 1 bytes. |
| CVE-2022-29526 | Medium | 2022-06-23 | Not applicable | No public exploit | Go before 1.17.10 and 1.18.x before 1.18.2 has Incorrect Privilege Assignment. When called with a non-zero flags parameter, the Faccessat function could incorrectly report that a file is accessible. |
| CVE-2022-28327 | High | 2022-04-20 | Not applicable | No public exploit | The generic P-256 feature in crypto/elliptic in Go before 1.17.9 and 1.18.x before 1.18.1 allows a panic via long scalar input. |
| CVE-2022-27536 | High | 2022-04-20 | Not applicable | No public exploit | Certificate.Verify in crypto/x509 in Go 1.18.x before 1.18.1 can be caused to panic on macOS when presented with certain malformed certificates. This allows a remote TLS server to cause a TLS client to panic. |
| CVE-2022-24675 | High | 2022-04-20 | Not applicable | No public exploit | encoding/pem in Go before 1.17.9 and 1.18.x before 1.18.1 has a Decode stack overflow via a large amount of PEM data. |
| CVE-2022-24921 | High | 2022-03-05 | Not applicable | No public exploit | regexp.Compile in Go before 1.16.15 and 1.17.x before 1.17.8 allows stack exhaustion via a deeply nested expression. |
| CVE-2022-23806 | Critical | 2022-02-11 | Not applicable | No public exploit | Curve.IsOnCurve in crypto/elliptic in Go before 1.16.14 and 1.17.x before 1.17.7 can incorrectly return true in situations with a big.Int value that is not a valid field element. |
| CVE-2022-23773 | High | 2022-02-11 | Not applicable | No public exploit | cmd/go in Go before 1.16.14 and 1.17.x before 1.17.7 can misinterpret branch names that falsely appear to be version tags. This can lead to incorrect access control if an actor is supposed to be able to create branches but not tags. |
| CVE-2022-23772 | High | 2022-02-11 | Not applicable | No public exploit | Rat.SetString in math/big in Go before 1.16.14 and 1.17.x before 1.17.7 has an overflow that can lead to Uncontrolled Memory Consumption. |
| CVE-2021-39293 | High | 2022-01-24 | Not applicable | No public exploit | In archive/zip in Go before 1.16.8 and 1.17.x before 1.17.1, a crafted archive header (falsely designating that many files are present) can cause a NewReader or OpenReader panic. NOTE: this issue exists because of an incomplete fix for CVE-2021-33196. |
| CVE-2021-44717 | Medium | 2022-01-01 | Not applicable | No public exploit | Go before 1.16.12 and 1.17.x before 1.17.5 on UNIX allows write operations to an unintended file or unintended network connection as a consequence of erroneous closing of file descriptor 0 after file-descriptor exhaustion. |
| CVE-2021-44716 | High | 2022-01-01 | Not applicable | No public exploit | net/http in Go before 1.16.12 and 1.17.x before 1.17.5 allows uncontrolled memory consumption in the header canonicalization cache via HTTP/2 requests. |
| CVE-2021-41772 | High | 2021-11-08 | Not applicable | No public exploit | Go before 1.16.10 and 1.17.x before 1.17.3 allows an archive/zip Reader.Open panic via a crafted ZIP archive containing an invalid name or an empty filename field. |
| CVE-2021-41771 | High | 2021-11-08 | Not applicable | No public exploit | ImportedSymbols in debug/macho (for Open or OpenFat) in Go before 1.16.10 and 1.17.x before 1.17.3 Accesses a Memory Location After the End of a Buffer, aka an out-of-bounds slice situation. |
| CVE-2021-38297 | Critical | 2021-10-18 | Not applicable | Proof of concept only | Go before 1.16.9 and 1.17.x before 1.17.2 has a Buffer Overflow via large arguments in a function invocation from a WASM module, when GOARCH=wasm GOOS=js is used. |
| CVE-2021-36221 | Medium | 2021-08-08 | Not applicable | No public exploit | Go before 1.15.15 and 1.16.x before 1.16.7 has a race condition that can lead to a net/http/httputil ReverseProxy panic upon an ErrAbortHandler abort. |
| CVE-2021-29923 | High | 2021-08-07 | Not applicable | No public exploit | Go before 1.17 does not properly consider extraneous zero characters at the beginning of an IP address octet, which (in some situations) allows attackers to bypass access control that is based on IP addresses, because of unexpected octal interpretation. This affects net.ParseIP and net.ParseCIDR. |
| CVE-2021-33198 | High | 2021-08-02 | Not applicable | No public exploit | In Go before 1.15.13 and 1.16.x before 1.16.5, there can be a panic for a large exponent to the math/big.Rat SetString or UnmarshalText method. |
| CVE-2021-33197 | Medium | 2021-08-02 | Not applicable | No public exploit | In Go before 1.15.13 and 1.16.x before 1.16.5, some configurations of ReverseProxy (from net/http/httputil) result in a situation where an attacker is able to drop arbitrary headers. |
| CVE-2021-33196 | High | 2021-08-02 | Not applicable | No public exploit | In archive/zip in Go before 1.15.13 and 1.16.x before 1.16.5, a crafted file count (in an archive's header) can cause a NewReader or OpenReader panic. |
| CVE-2021-33195 | High | 2021-08-02 | Not applicable | No public exploit | Go before 1.15.13 and 1.16.x before 1.16.5 has functions for DNS lookups that do not validate replies from DNS servers, and thus a return value may contain an unsafe injection (e.g., XSS) that does not conform to the RFC1035 format. |
| CVE-2021-34558 | Medium | 2021-07-15 | Not applicable | Proof of concept only | The crypto/tls package of Go through 1.16.5 does not properly assert that the type of public key in an X.509 certificate matches the expected type when doing a RSA based key exchange, allowing a malicious TLS server to cause a TLS client to panic. |
| CVE-2012-2666 | Critical | 2021-07-09 | Not applicable | No public exploit | golang/go in 1.0.2 fixes all.bash on shared machines. dotest() in src/pkg/debug/gosym/pclntab_test.go creates a temporary file with predicable name and executes it as shell script. |
| CVE-2021-31525 | Medium | 2021-05-27 | Not applicable | No public exploit | net/http in Go before 1.15.12 and 1.16.x before 1.16.4 allows remote attackers to cause a denial of service (panic) via a large header to ReadRequest or ReadResponse. Server, Transport, and Client can each be affected in some configurations. |
| CVE-2021-33194 | High | 2021-05-26 | Not applicable | No public exploit | golang.org/x/net before v0.0.0-20210520170846-37e1c6afe023 allows attackers to cause a denial of service (infinite loop) via crafted ParseFragment input. |
| CVE-2021-27919 | Medium | 2021-03-11 | Not applicable | No public exploit | archive/zip in Go 1.16.x before 1.16.1 allows attackers to cause a denial of service (panic) upon attempted use of the Reader.Open API for a ZIP archive in which ../ occurs at the beginning of any filename. |
| CVE-2021-27918 | High | 2021-03-11 | Not applicable | No public exploit | encoding/xml in Go before 1.15.9 and 1.16.x before 1.16.1 has an infinite loop if a custom TokenReader (for xml.NewTokenDecoder) returns EOF in the middle of an element. This can occur in the Decode, DecodeElement, or Skip method. |
| CVE-2021-3115 | High | 2021-01-26 | Not applicable | No public exploit | Go before 1.14.14 and 1.15.x before 1.15.7 on Windows is vulnerable to Command Injection and remote code execution when using the "go get" command to fetch modules that make use of cgo (for example, cgo can execute a gcc program from an untrusted download). |
| CVE-2021-3114 | Medium | 2021-01-26 | Not applicable | No public exploit | In Go before 1.14.14 and 1.15.x before 1.15.7, crypto/elliptic/p224.go can generate incorrect outputs, related to an underflow of the lowest limb during the final complete reduction in the P-224 field. |
| CVE-2020-28851 | High | 2021-01-02 | Not applicable | No public exploit | In x/text in Go 1.15.4, an "index out of range" panic occurs in language.ParseAcceptLanguage while parsing the -u- extension. (x/text/language is supposed to be able to parse an HTTP Accept-Language header.) |
| CVE-2020-29511 | Critical | 2020-12-14 | Not applicable | No public exploit | The encoding/xml package in Go (all versions) does not correctly preserve the semantics of element namespace prefixes during tokenization round-trips, which allows an attacker to craft inputs that behave in conflicting ways during different stages of processing in affected downstream applications. |
| CVE-2020-29510 | Critical | 2020-12-14 | Not applicable | No public exploit | 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 an attacker to craft inputs that behave in conflicting ways during different stages of processing in affected downstream applications. |
| CVE-2020-29509 | Critical | 2020-12-14 | Not applicable | No public exploit | The encoding/xml package in Go (all versions) does not correctly preserve the semantics of attribute namespace prefixes during tokenization round-trips, which allows an attacker to craft inputs that behave in conflicting ways during different stages of processing in affected downstream applications. |
| CVE-2020-28367 | High | 2020-11-18 | Not applicable | No public exploit | 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 #cgo directive. |
| CVE-2020-28366 | High | 2020-11-18 | Not applicable | No public exploit | 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 a linked object file. |
| CVE-2020-28362 | High | 2020-11-18 | Not applicable | No public exploit | Go before 1.14.12 and 1.15.x before 1.15.4 allows Denial of Service. |
| CVE-2020-24553 | Medium | 2020-09-02 | Not applicable | No public exploit | 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. |
| CVE-2020-16845 | High | 2020-08-06 | Not applicable | No public exploit | Go before 1.13.15 and 14.x before 1.14.7 can have an infinite read loop in ReadUvarint and ReadVarint in encoding/binary via invalid inputs. |
| CVE-2020-15586 | Medium | 2020-07-17 | Not applicable | No public exploit | 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 request body and writes a response at the same time. |
| CVE-2020-14039 | Medium | 2020-07-17 | Not applicable | No public exploit | 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 equals nil and the installation is on Windows). Thus, X.509 certificate verification is incomplete. |
| CVE-2020-7919 | High | 2020-03-16 | Not applicable | No public exploit | Go before 1.12.16 and 1.13.x before 1.13.7 (and the crypto/cryptobyte package before 0.0.0-20200124225646-8b5121be2f68 for Go) allows attacks on clients (resulting in a panic) via a malformed X.509 certificate. |
| CVE-2015-5741 | Critical | 2020-02-08 | 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 that contains Content-Length and Transfer-Encoding header fields. |
| CVE-2020-0601 | High | 2020-01-14 | Not applicable | Exploited | A spoofing vulnerability exists in the way Windows CryptoAPI (Crypt32.dll) validates Elliptic Curve Cryptography (ECC) certificates.An attacker could exploit the vulnerability by using a spoofed code-signing certificate to sign a malicious executable, making it appear the file was from a trusted, legitimate source, aka 'Windows CryptoAPI Spoofing Vulnerability'. |
| CVE-2019-17596 | High | 2019-10-24 | Not applicable | No public exploit | 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. There are several attack scenarios, such as traffic from a client to a server that verifies client certificates. |
| CVE-2019-16276 | High | 2019-09-30 | Not applicable | No public exploit | Go before 1.12.10 and 1.13.x before 1.13.1 allow HTTP Request Smuggling. |
| CVE-2019-14809 | Critical | 2019-08-13 | Not applicable | No public exploit | 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. This is related to a Host field with a suffix appearing in neither Hostname() nor Port(), and is related to a non-numeric port number. For example, an attacker can compose a crafted javascript:// URL that results in a hostname of google.com. |
| CVE-2019-11888 | Critical | 2019-05-13 | Not applicable | No public exploit | 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 information or gain privileges. |
| CVE-2019-9741 | Medium | 2019-03-13 | Not applicable | No public exploit | An issue was discovered in net/http in Go 1.11.5. CRLF injection is possible if the attacker controls a url parameter, as demonstrated by the second argument to http.NewRequest with \r\n followed by an HTTP header or a Redis command. |
| CVE-2019-9634 | High | 2019-03-08 | Not applicable | No public exploit | Go through 1.12 on Windows misuses certain LoadLibrary functionality, leading to DLL injection. |
| CVE-2019-6486 | High | 2019-01-24 | Not applicable | No public exploit | 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 possibly conduct ECDH private key recovery attacks. |
| CVE-2018-16875 | High | 2018-12-14 | Not applicable | Proof of concept only | The crypto/x509 package of Go before 1.10.6 and 1.11.x before 1.11.3 does not limit the amount of work performed for each chain verification, which might allow attackers to craft pathological inputs leading to a CPU denial of service. Go TLS servers accepting client certificates and TLS clients are affected. |
| 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-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-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. |