Source: golang-1.13 Version: 1.13~beta1-2 Severity: grave Tags: security upstream Justification: user security hole Forwarded: https://github.com/golang/go/issues/33606
Hi, The following vulnerabilities were published for golang-1.13. The recent issues exits as well in the current present version of golang-1.13 in unstable and bullseye. CVE-2019-9512[0]: | Some HTTP/2 implementations are vulnerable to ping floods, potentially | leading to a denial of service. The attacker sends continual pings to | an HTTP/2 peer, causing the peer to build an internal queue of | responses. Depending on how efficiently this data is queued, this can | consume excess CPU, memory, or both. CVE-2019-9514[1]: | Some HTTP/2 implementations are vulnerable to a reset flood, | potentially leading to a denial of service. The attacker opens a | number of streams and sends an invalid request over each stream that | should solicit a stream of RST_STREAM frames from the peer. Depending | on how the peer queues the RST_STREAM frames, this can consume excess | memory, CPU, or both. If you fix the vulnerabilities please also make sure to include the CVE (Common Vulnerabilities & Exposures) ids in your changelog entry. For further information see: [0] https://security-tracker.debian.org/tracker/CVE-2019-9512 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9512 [1] https://security-tracker.debian.org/tracker/CVE-2019-9514 https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-9514 [2] https://github.com/golang/go/issues/33606 Regards, Salvatore
