Описание
When an OAuth2 bearer token is used for an HTTP(S) transfer, and that transfer performs a cross-protocol redirect to a second URL that uses an IMAP, LDAP, POP3 or SMTP scheme, curl might wrongly pass on the bearer token to the new target host.
| Релиз | Статус | Примечание |
|---|---|---|
| devel | not-affected | 8.18.0 |
| esm-infra-legacy/trusty | ignored | changes too intrusive |
| esm-infra-legacy/xenial | ignored | changes too intrusive |
| esm-infra/bionic | ignored | changes too intrusive |
| esm-infra/focal | ignored | changes too intrusive |
| esm-infra/xenial | ignored | end of ESM support, was ignored [changes too intrusive] |
| jammy | released | 7.81.0-1ubuntu1.22 |
| noble | released | 8.5.0-2ubuntu10.7 |
| plucky | ignored | end of life, was needed |
| questing | released | 8.14.1-2ubuntu1.1 |
Показывать по
EPSS
5.3 Medium
CVSS3
Связанные уязвимости
When an OAuth2 bearer token is used for an HTTP(S) transfer, and that transfer performs a cross-protocol redirect to a second URL that uses an IMAP, LDAP, POP3 or SMTP scheme, curl might wrongly pass on the bearer token to the new target host.
When an OAuth2 bearer token is used for an HTTP(S) transfer, and that transfer performs a cross-protocol redirect to a second URL that uses an IMAP, LDAP, POP3 or SMTP scheme, curl might wrongly pass on the bearer token to the new target host.
When an OAuth2 bearer token is used for an HTTP(S) transfer, and that ...
When an OAuth2 bearer token is used for an HTTP(S) transfer, and that transfer performs a cross-protocol redirect to a second URL that uses an IMAP, LDAP, POP3 or SMTP scheme, curl might wrongly pass on the bearer token to the new target host.
EPSS
5.3 Medium
CVSS3