ID CVE-2019-17596
Summary 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.
References
Vulnerable Configurations
  • cpe:2.3:a:golang:go:1.12:*:*:*:*:*:*:*
    cpe:2.3:a:golang:go:1.12:*:*:*:*:*:*:*
  • cpe:2.3:a:golang:go:1.12:-:*:*:*:*:*:*
    cpe:2.3:a:golang:go:1.12:-:*:*:*:*:*:*
  • cpe:2.3:a:golang:go:1.12:beta1:*:*:*:*:*:*
    cpe:2.3:a:golang:go:1.12:beta1:*:*:*:*:*:*
  • cpe:2.3:a:golang:go:1.12:beta2:*:*:*:*:*:*
    cpe:2.3:a:golang:go:1.12:beta2:*:*:*:*:*:*
  • cpe:2.3:a:golang:go:1.12:rc1:*:*:*:*:*:*
    cpe:2.3:a:golang:go:1.12:rc1:*:*:*:*:*:*
  • cpe:2.3:a:golang:go:1.12.0:*:*:*:*:*:*:*
    cpe:2.3:a:golang:go:1.12.0:*:*:*:*:*:*:*
  • cpe:2.3:a:golang:go:1.12.0:-:*:*:*:*:*:*
    cpe:2.3:a:golang:go:1.12.0:-:*:*:*:*:*:*
  • cpe:2.3:a:golang:go:1.12.0:beta1:*:*:*:*:*:*
    cpe:2.3:a:golang:go:1.12.0:beta1:*:*:*:*:*:*
  • cpe:2.3:a:golang:go:1.12.0:beta2:*:*:*:*:*:*
    cpe:2.3:a:golang:go:1.12.0:beta2:*:*:*:*:*:*
  • cpe:2.3:a:golang:go:1.12.0:rc1:*:*:*:*:*:*
    cpe:2.3:a:golang:go:1.12.0:rc1:*:*:*:*:*:*
  • cpe:2.3:a:golang:go:1.12.1:*:*:*:*:*:*:*
    cpe:2.3:a:golang:go:1.12.1:*:*:*:*:*:*:*
  • cpe:2.3:a:golang:go:1.12.2:*:*:*:*:*:*:*
    cpe:2.3:a:golang:go:1.12.2:*:*:*:*:*:*:*
  • cpe:2.3:a:golang:go:1.12.3:*:*:*:*:*:*:*
    cpe:2.3:a:golang:go:1.12.3:*:*:*:*:*:*:*
  • cpe:2.3:a:golang:go:1.12.4:*:*:*:*:*:*:*
    cpe:2.3:a:golang:go:1.12.4:*:*:*:*:*:*:*
  • cpe:2.3:a:golang:go:1.12.5:*:*:*:*:*:*:*
    cpe:2.3:a:golang:go:1.12.5:*:*:*:*:*:*:*
  • cpe:2.3:a:golang:go:1.12.6:*:*:*:*:*:*:*
    cpe:2.3:a:golang:go:1.12.6:*:*:*:*:*:*:*
  • cpe:2.3:a:golang:go:1.12.7:*:*:*:*:*:*:*
    cpe:2.3:a:golang:go:1.12.7:*:*:*:*:*:*:*
  • cpe:2.3:a:golang:go:1.12.8:*:*:*:*:*:*:*
    cpe:2.3:a:golang:go:1.12.8:*:*:*:*:*:*:*
  • cpe:2.3:a:golang:go:1.12.9:*:*:*:*:*:*:*
    cpe:2.3:a:golang:go:1.12.9:*:*:*:*:*:*:*
  • cpe:2.3:a:golang:go:1.12.10:*:*:*:*:*:*:*
    cpe:2.3:a:golang:go:1.12.10:*:*:*:*:*:*:*
  • cpe:2.3:a:golang:go:1.13:-:*:*:*:*:*:*
    cpe:2.3:a:golang:go:1.13:-:*:*:*:*:*:*
  • cpe:2.3:a:golang:go:1.13:beta1:*:*:*:*:*:*
    cpe:2.3:a:golang:go:1.13:beta1:*:*:*:*:*:*
  • cpe:2.3:a:golang:go:1.13:rc1:*:*:*:*:*:*
    cpe:2.3:a:golang:go:1.13:rc1:*:*:*:*:*:*
  • cpe:2.3:a:golang:go:1.13:rc2:*:*:*:*:*:*
    cpe:2.3:a:golang:go:1.13:rc2:*:*:*:*:*:*
  • cpe:2.3:a:golang:go:1.13.1:*:*:*:*:*:*:*
    cpe:2.3:a:golang:go:1.13.1:*:*:*:*:*:*:*
  • cpe:2.3:o:debian:debian_linux:10:*:*:*:*:*:*:*
    cpe:2.3:o:debian:debian_linux:10:*:*:*:*:*:*:*
CVSS
Base: 5.0 (as of 31-10-2019 - 04:15)
Impact:
Exploitability:
CWE CWE-436
CAPEC
  • HTTP Request Splitting
    HTTP Request Splitting (also known as HTTP Request Smuggling) is an attack pattern where an attacker attempts to insert additional HTTP requests in the body of the original (enveloping) HTTP request in such a way that the browser interprets it as one request but the web server interprets it as two. There are several ways to perform HTTP request splitting attacks. One way is to include double Content-Length headers in the request to exploit the fact that the devices parsing the request may each use a different header. Another way is to submit an HTTP request with a "Transfer Encoding: chunked" in the request header set with setRequestHeader to allow a payload in the HTTP Request that can be considered as another HTTP Request by a subsequent parsing entity. A third way is to use the "Double CR in an HTTP header" technique. There are also a few less general techniques targeting specific parsing vulnerabilities in certain web servers.
  • HTTP Response Smuggling
    An attacker injects content into a server response that is interpreted differently by intermediaries than it is by the target browser. To do this, it takes advantage of inconsistent or incorrect interpretations of the HTTP protocol by various applications. For example, it might use different block terminating characters (CR or LF alone), adding duplicate header fields that browsers interpret as belonging to separate responses, or other techniques. Consequences of this attack can include response-splitting, cross-site scripting, apparent defacement of targeted sites, cache poisoning, or similar actions.
  • HTTP Request Smuggling
    HTTP Request Smuggling results from the discrepancies in parsing HTTP requests between HTTP entities such as web caching proxies or application firewalls. Entities such as web servers, web caching proxies, application firewalls or simple proxies often parse HTTP requests in slightly different ways. Under specific situations where there are two or more such entities in the path of the HTTP request, a specially crafted request is seen by two attacked entities as two different sets of requests. This allows certain requests to be smuggled through to a second entity without the first one realizing it.
Access
VectorComplexityAuthentication
NETWORK LOW NONE
Impact
ConfidentialityIntegrityAvailability
NONE NONE PARTIAL
cvss-vector via4 AV:N/AC:L/Au:N/C:N/I:N/A:P
Last major update 31-10-2019 - 04:15
Published 24-10-2019 - 22:15
Last modified 31-10-2019 - 04:15
Back to Top