Http2 vulnerabilitiesAnd the versions its exploited flaws hit.

Product1 known exploited17 versions
The short answer

Http2 is made by Golang. We track 4 published vulnerabilities in it, across 17 versions. 1 of them is on the list of flaws known to be exploited, the newest added on 10 October 2023. If you run Http2, check your version against the exploited flaws below and patch those first.

Check your version

The most recent Http2 flaw added to the known-exploited list is CVE-2023-44487, on 10 October 2023. We keep watching the known-exploited list.

Versions

Which versions of Http2 do the exploited flaws hit?

Each exploited flaw lists the versions it affects, usually as ranges. "before 0.17.0" means every version up to, but not including, 0.17.0. Find your version, then patch.

  • CVE-2023-44487Exploited list, 10 Oct 2023

    HTTP/2 Rapid Reset Attack Vulnerability

    before 0.17.0
Known exploited

Which Http2 vulnerabilities are being exploited?

1 flaw is on the government list of vulnerabilities known to be exploited. These are the ones criminals are using now, so they go first, whatever their severity score says.

  1. 7.5
    CVE-2023-44487HighKnown exploited
    HTTP/2 Rapid Reset Attack Vulnerability

    HTTP/2 contains a rapid reset vulnerability that allows for a distributed denial-of-service attack (DDoS).

    Chance of use>99%Known exploited since10 Oct 2023
Exploit likelihood

Which Http2 flaws are most likely to be used?

Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.

50% or more10% to 49%Under 10%
  1. >99%
    CVE-2023-44487HighKnown exploited

    The HTTP/2 protocol allows a denial of service (server resource consumption) because request cancellation can reset many streams quickly, as exploited in the wild in August through October 2023.

    CVSS7.5Published10 Oct 2023
  2. 6.1%

    An attacker can cause excessive memory growth in a Go server accepting HTTP/2 requests.

    CVSS5.3Published8 Dec 2022
  3. 4.6%

    A maliciously crafted HTTP/2 stream could cause excessive CPU consumption in the HPACK decoder, sufficient to cause a denial of service from a small number of small requests.

    CVSS7.5Published28 Feb 2023
  4. 3.8%

    A malicious HTTP/2 client which rapidly creates requests and immediately resets them can cause excessive server resource consumption.

    CVSS7.5Published11 Oct 2023
Precursor Intelligence

Running Http2? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

We track 4 published vulnerabilities listed under the name Http2, across 17 versions. The most recent Http2 flaw added to the known-exploited list is CVE-2023-44487, on 10 October 2023.

1 is on the list of flaws known to be exploited. The most recently added is CVE-2023-44487.

Each flaw names its own versions, usually as ranges. The newest, CVE-2023-44487, affects before 0.17.0. The versions for every exploited flaw are listed on this page.

Create a Precursor Intelligence account and track Http2. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.