CVE-2019-9515highCWE-400

Some HTTP/2 implementations are vulnerable to a settings flood, potentially leading to a denial of service

43Vexday Risk Score

No sign of exploitation. No public exploitation artifact known so far.

ssvc Trackcvss 7.5epss 87%

exploitation probability

87%top 1% of all CVEs

observed exploitation

nono source reports it

What the vendors declare (VEX)

Official vendor statements in CSAF/VEX format: whether their product is affected, already fixed, or ruled out — and why. These are the vendor's assertions, not Vexday's judgment.

Red HatVEX document ↗

Affected

5 products (12 components)

Red Hat OpenShift Application Runtimes · Red Hat OpenShift Container Platform 4 · Red Hat AMQ Broker 7 · Red Hat Ceph Storage 3 · Red Hat JBoss Fuse 6

none_available: Affected

Fixed

27 products (706 components)

Red Hat JBoss EAP 7.2 for RHEL 7 Server · Red Hat JBoss EAP 7.2 for RHEL 6 Server · Red Hat JBoss EAP 7.2 for RHEL 8 · Red Hat Software Collections for Red Hat Enterprise Linux Server (v. 7) · Red Hat Software Collections for Red Hat Enterprise Linux Server EUS (v. 7.5) · and others 22

fix ↗

Not affected

16 products (115 components) — because the vulnerable code is not present in the product

Red Hat Software Collections · Red Hat OpenShift Container Platform 3.9 · Red Hat OpenShift Container Platform 3.10 · Red Hat OpenShift Container Platform 3.11 · Red Hat OpenShift Container Platform 4 · and others 11

Some HTTP/2 implementations are vulnerable to a settings flood, potentially leading to a denial of service. The attacker sends a stream of SETTINGS frames to the peer. Since the RFC requires that the peer reply with one acknowledgement per SETTINGS frame, an empty SETTINGS frame is almost equivalent in behavior to a ping. Depending on how efficiently this data is queued, this can consume excess CPU, memory, or both.

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected products

n/a · n/a

References