Описание
For requests that have a body, but reading the body may end up in reading 0 bytes, there is a buffer leak. This is particularly the case for 100-Continue, but any request where the network is slow can leak.
Пакеты
| Пакет | Статус | Версия исправления | Релиз | Тип |
|---|---|---|---|---|
| jetty12 | undetermined | package | ||
| jetty9 | undetermined | package |
Примечания
https://github.com/jetty/jetty.project/security/advisories/GHSA-9299-c6m4-mjhc
https://github.com/jetty/jetty.project/pull/12156
Связанные уязвимости
For requests that have a body, but reading the body may end up in reading 0 bytes, there is a buffer leak. This is particularly the case for 100-Continue, but any request where the network is slow can leak.
For requests that have a body, but reading the body may end up in reading 0 bytes, there is a buffer leak. This is particularly the case for 100-Continue, but any request where the network is slow can leak.
For requests that have a body, but reading the body may end up in reading 0 bytes, there is a buffer leak. This is particularly the case for 100-Continue, but any request where the network is slow can leak.
Eclipse Jetty: DoS attack triggering OutOfMemory with 100-Continue requests