Описание
The HTTP client drops sensitive headers after following a cross-domain redirect. For example, a request to a.com/ containing an Authorization header which is redirected to b.com/ will not send that header to b.com. In the event that the client received a subsequent same-domain redirect, however, the sensitive headers would be restored. For example, a chain of redirects from a.com/, to b.com/1, and finally to b.com/2 would incorrectly send the Authorization header to b.com/2.
Релиз | Статус | Примечание |
---|---|---|
bionic | DNE | |
devel | DNE | |
esm-infra-legacy/trusty | DNE | |
esm-infra/focal | DNE | |
focal | DNE | |
jammy | DNE | |
noble | DNE | |
oracular | DNE | |
plucky | DNE | |
trusty | ignored | end of standard support |
Показывать по
Релиз | Статус | Примечание |
---|---|---|
bionic | ignored | end of standard support |
devel | DNE | |
esm-infra-legacy/trusty | needs-triage | |
esm-infra/bionic | needs-triage | |
esm-infra/focal | DNE | |
esm-infra/xenial | needs-triage | |
focal | DNE | |
jammy | DNE | |
noble | DNE | |
oracular | DNE |
Показывать по
Релиз | Статус | Примечание |
---|---|---|
bionic | ignored | end of standard support |
devel | DNE | |
esm-apps/bionic | needs-triage | |
esm-apps/jammy | needs-triage | |
esm-apps/xenial | needs-triage | |
esm-infra-legacy/trusty | DNE | |
esm-infra/focal | needs-triage | |
focal | ignored | end of standard support, was needs-triage |
jammy | needs-triage | |
noble | DNE |
Показывать по
Релиз | Статус | Примечание |
---|---|---|
bionic | DNE | |
devel | DNE | |
esm-infra-legacy/trusty | DNE | |
esm-infra/focal | needs-triage | |
focal | ignored | end of standard support, was needs-triage |
jammy | DNE | |
noble | DNE | |
oracular | DNE | |
plucky | DNE | |
trusty | DNE |
Показывать по
Релиз | Статус | Примечание |
---|---|---|
bionic | ignored | end of standard support |
devel | DNE | |
esm-apps/bionic | needs-triage | |
esm-apps/focal | needs-triage | |
focal | ignored | end of standard support, was needs-triage |
jammy | DNE | |
noble | DNE | |
oracular | DNE | |
plucky | DNE | |
trusty | DNE |
Показывать по
Релиз | Статус | Примечание |
---|---|---|
bionic | DNE | |
devel | DNE | |
esm-infra/focal | DNE | |
focal | DNE | |
jammy | needs-triage | |
noble | DNE | |
oracular | DNE | |
plucky | DNE | |
trusty | DNE | |
upstream | needs-triage |
Показывать по
Релиз | Статус | Примечание |
---|---|---|
bionic | ignored | end of standard support |
devel | DNE | |
esm-apps/bionic | needs-triage | |
esm-apps/xenial | needs-triage | |
esm-infra/focal | DNE | focal was needs-triage |
focal | ignored | end of standard support, was needs-triage |
jammy | needs-triage | |
noble | DNE | |
oracular | DNE | |
plucky | DNE |
Показывать по
Релиз | Статус | Примечание |
---|---|---|
bionic | DNE | |
devel | DNE | |
esm-infra/focal | DNE | |
focal | DNE | |
jammy | DNE | |
noble | DNE | |
oracular | DNE | |
plucky | DNE | |
trusty | DNE | |
upstream | needs-triage |
Показывать по
Релиз | Статус | Примечание |
---|---|---|
bionic | DNE | |
devel | DNE | |
esm-infra/focal | DNE | focal was needs-triage |
focal | ignored | end of standard support, was needs-triage |
jammy | needs-triage | |
noble | DNE | |
oracular | DNE | |
plucky | DNE | |
trusty | DNE | |
upstream | needs-triage |
Показывать по
Релиз | Статус | Примечание |
---|---|---|
bionic | DNE | |
devel | DNE | |
esm-apps/noble | needs-triage | |
esm-infra/focal | DNE | focal was needs-triage |
focal | ignored | end of standard support, was needs-triage |
jammy | needs-triage | |
noble | needs-triage | |
oracular | DNE | |
plucky | DNE | |
trusty | DNE |
Показывать по
Релиз | Статус | Примечание |
---|---|---|
devel | DNE | |
esm-infra/focal | DNE | focal was needs-triage |
focal | ignored | end of standard support, was needs-triage |
jammy | released | 1.22.2-2~22.04.3 |
noble | released | 1.22.2-2ubuntu0.4 |
oracular | released | 1.22.8-1ubuntu0.1 |
plucky | DNE | |
upstream | released | 1.22.11-1 |
Показывать по
Релиз | Статус | Примечание |
---|---|---|
devel | not-affected | 1.23.5-1 |
esm-infra/focal | DNE | |
focal | DNE | |
jammy | needs-triage | |
noble | needs-triage | |
oracular | needs-triage | |
plucky | not-affected | 1.23.5-1 |
upstream | released | 1.23.5-1 |
Показывать по
Релиз | Статус | Примечание |
---|---|---|
devel | needs-triage | |
esm-infra/focal | DNE | |
focal | DNE | |
jammy | DNE | |
noble | DNE | |
oracular | DNE | |
plucky | needs-triage | |
upstream | needs-triage |
Показывать по
Релиз | Статус | Примечание |
---|---|---|
bionic | DNE | |
devel | DNE | |
esm-infra-legacy/trusty | DNE | |
esm-infra/focal | DNE | |
esm-infra/xenial | needs-triage | |
focal | DNE | |
jammy | DNE | |
noble | DNE | |
oracular | DNE | |
plucky | DNE |
Показывать по
Релиз | Статус | Примечание |
---|---|---|
bionic | ignored | end of standard support |
devel | DNE | |
esm-apps/bionic | needs-triage | |
esm-infra-legacy/trusty | DNE | |
esm-infra/focal | DNE | |
focal | DNE | |
jammy | DNE | |
noble | DNE | |
oracular | DNE | |
plucky | DNE |
Показывать по
Релиз | Статус | Примечание |
---|---|---|
bionic | ignored | end of standard support |
devel | DNE | |
esm-apps/bionic | needs-triage | |
esm-infra-legacy/trusty | DNE | |
esm-infra/focal | DNE | |
focal | DNE | |
jammy | DNE | |
noble | DNE | |
oracular | DNE | |
plucky | DNE |
Показывать по
EPSS
6.1 Medium
CVSS3
Связанные уязвимости
The HTTP client drops sensitive headers after following a cross-domain redirect. For example, a request to a.com/ containing an Authorization header which is redirected to b.com/ will not send that header to b.com. In the event that the client received a subsequent same-domain redirect, however, the sensitive headers would be restored. For example, a chain of redirects from a.com/, to b.com/1, and finally to b.com/2 would incorrectly send the Authorization header to b.com/2.
The HTTP client drops sensitive headers after following a cross-domain redirect. For example, a request to a.com/ containing an Authorization header which is redirected to b.com/ will not send that header to b.com. In the event that the client received a subsequent same-domain redirect, however, the sensitive headers would be restored. For example, a chain of redirects from a.com/, to b.com/1, and finally to b.com/2 would incorrectly send the Authorization header to b.com/2.
The HTTP client drops sensitive headers after following a cross-domain ...
The HTTP client drops sensitive headers after following a cross-domain redirect. For example, a request to a.com/ containing an Authorization header which is redirected to b.com/ will not send that header to b.com. In the event that the client received a subsequent same-domain redirect, however, the sensitive headers would be restored. For example, a chain of redirects from a.com/, to b.com/1, and finally to b.com/2 would incorrectly send the Authorization header to b.com/2.
EPSS
6.1 Medium
CVSS3