Описание
Werkzeug is a comprehensive WSGI web application library. Browsers may allow "nameless" cookies that look like =value
instead of key=value
. A vulnerable browser may allow a compromised application on an adjacent subdomain to exploit this to set a cookie like =__Host-test=bad
for another subdomain. Werkzeug prior to 2.2.3 will parse the cookie =__Host-test=bad
as __Host-test=bad`. If a Werkzeug application is running next to a vulnerable or malicious subdomain which sets such a cookie using a vulnerable browser, the Werkzeug application will see the bad cookie value but the valid cookie key. The issue is fixed in Werkzeug 2.2.3.
Релиз | Статус | Примечание |
---|---|---|
bionic | released | 0.14.1+dfsg1-1ubuntu0.2 |
devel | not-affected | 2.2.2-3 |
esm-infra/bionic | not-affected | 0.14.1+dfsg1-1ubuntu0.2 |
esm-infra/focal | not-affected | 0.16.1+dfsg1-2ubuntu0.1 |
esm-infra/xenial | released | 0.10.4+dfsg1-1ubuntu1.2+esm1 |
focal | released | 0.16.1+dfsg1-2ubuntu0.1 |
jammy | released | 2.0.2+dfsg1-1ubuntu0.22.04.1 |
kinetic | released | 2.0.2+dfsg1-3ubuntu0.22.10.1 |
lunar | released | 2.2.2-2ubuntu0.1 |
trusty | ignored | end of standard support |
Показывать по
Ссылки на источники
2.6 Low
CVSS3
Связанные уязвимости
Werkzeug is a comprehensive WSGI web application library. Browsers may allow "nameless" cookies that look like `=value` instead of `key=value`. A vulnerable browser may allow a compromised application on an adjacent subdomain to exploit this to set a cookie like `=__Host-test=bad` for another subdomain. Werkzeug prior to 2.2.3 will parse the cookie `=__Host-test=bad` as __Host-test=bad`. If a Werkzeug application is running next to a vulnerable or malicious subdomain which sets such a cookie using a vulnerable browser, the Werkzeug application will see the bad cookie value but the valid cookie key. The issue is fixed in Werkzeug 2.2.3.
Werkzeug is a comprehensive WSGI web application library. Browsers may allow "nameless" cookies that look like `=value` instead of `key=value`. A vulnerable browser may allow a compromised application on an adjacent subdomain to exploit this to set a cookie like `=__Host-test=bad` for another subdomain. Werkzeug prior to 2.2.3 will parse the cookie `=__Host-test=bad` as __Host-test=bad`. If a Werkzeug application is running next to a vulnerable or malicious subdomain which sets such a cookie using a vulnerable browser, the Werkzeug application will see the bad cookie value but the valid cookie key. The issue is fixed in Werkzeug 2.2.3.
Werkzeug is a comprehensive WSGI web application library. Browsers may ...
Incorrect parsing of nameless cookies leads to __Host- cookies bypass
2.6 Low
CVSS3