Описание
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.
| Релиз | Статус | Примечание |
|---|---|---|
| bionic | ignored | end of standard support, was needed |
| cosmic | ignored | end of life |
| devel | needed | |
| disco | ignored | end of life |
| eoan | ignored | end of life |
| esm-apps/bionic | needed | |
| esm-apps/focal | needed | |
| esm-apps/jammy | needed | |
| esm-apps/noble | needed | |
| esm-apps/xenial | needed |
Показывать по
| Релиз | Статус | Примечание |
|---|---|---|
| bionic | ignored | end of standard support, was needed |
| cosmic | ignored | end of life |
| devel | needed | |
| disco | ignored | end of life |
| eoan | ignored | end of life |
| esm-apps/bionic | needed | |
| esm-apps/focal | needed | |
| esm-apps/jammy | needed | |
| esm-apps/noble | needed | |
| esm-apps/xenial | needed |
Показывать по
| Релиз | Статус | Примечание |
|---|---|---|
| bionic | ignored | end of standard support, was needed |
| devel | DNE | |
| disco | released | 2.2.5+dfsg2-2+deb10u1build0.19.04.1 |
| eoan | not-affected | 2.2.5+dfsg2-3 |
| esm-apps/bionic | needed | |
| esm-apps/focal | not-affected | 2.2.5+dfsg2-3 |
| esm-apps/jammy | not-affected | 2.2.5+dfsg2-3 |
| esm-apps/noble | not-affected | 2.2.5+dfsg2-3 |
| esm-infra-legacy/trusty | DNE | |
| focal | not-affected | 2.2.5+dfsg2-3 |
Показывать по
| Релиз | Статус | Примечание |
|---|---|---|
| bionic | ignored | end of standard support, was needed |
| cosmic | ignored | end of life |
| devel | not-affected | |
| disco | ignored | end of life |
| eoan | ignored | end of life |
| esm-apps/bionic | released | 1:4.1.7-4ubuntu0.1+esm1 |
| esm-apps/focal | not-affected | |
| esm-apps/jammy | not-affected | |
| esm-apps/noble | not-affected | |
| esm-apps/xenial | not-affected | http2 support not implemented |
Показывать по
| Релиз | Статус | Примечание |
|---|---|---|
| bionic | not-affected | fixed for CVE-2018-16844 |
| cosmic | not-affected | fixed for CVE-2018-16844 |
| devel | not-affected | fixed for CVE-2018-16844 |
| disco | not-affected | fixed for CVE-2018-16844 |
| eoan | not-affected | fixed for CVE-2018-16844 |
| esm-infra-legacy/trusty | not-affected | http2 support not implemented |
| esm-infra/bionic | not-affected | fixed for CVE-2018-16844 |
| esm-infra/focal | not-affected | fixed for CVE-2018-16844 |
| esm-infra/xenial | not-affected | fixed for CVE-2018-16844 |
| focal | not-affected | fixed for CVE-2018-16844 |
Показывать по
| Релиз | Статус | Примечание |
|---|---|---|
| bionic | ignored | end of standard support, was needed |
| cosmic | ignored | end of life |
| devel | not-affected | 8.0.5+ds-1 |
| disco | ignored | end of life |
| eoan | not-affected | 8.0.5+ds-1 |
| esm-apps/bionic | needed | |
| esm-apps/focal | not-affected | 8.0.5+ds-1 |
| esm-apps/jammy | not-affected | 8.0.5+ds-1 |
| esm-apps/noble | not-affected | 8.0.5+ds-1 |
| esm-apps/xenial | needs-triage |
Показывать по
| Релиз | Статус | Примечание |
|---|---|---|
| bionic | released | 17.9.0-2ubuntu0.1 |
| cosmic | ignored | end of life |
| devel | released | 18.9.0-6ubuntu1 |
| disco | ignored | end of life |
| eoan | released | 18.9.0-3ubuntu1.1 |
| esm-infra-legacy/trusty | not-affected | http2 support not implemented |
| esm-infra/bionic | released | 17.9.0-2ubuntu0.1 |
| esm-infra/focal | released | 18.9.0-6ubuntu1 |
| esm-infra/xenial | not-affected | http2 support not implemented |
| focal | released | 18.9.0-6ubuntu1 |
Показывать по
Ссылки на источники
EPSS
7.8 High
CVSS2
7.5 High
CVSS3
Связанные уязвимости
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.
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.
Some HTTP/2 implementations are vulnerable to a settings flood, potent ...
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.
Уязвимость компонента connection.c сетевого протокола HTTP/2 веб-сервера Apache Traffic Server, веб-сервера H2O, программной платформы Node.js, сетевого программного средства SwiftNIO, позволяющая нарушителю вызвать отказ в обслуживании
EPSS
7.8 High
CVSS2
7.5 High
CVSS3