Описание
If a web application sends a WebSocket message concurrently with the WebSocket connection closing when running on Apache Tomcat 8.5.0 to 8.5.75 or Apache Tomcat 9.0.0.M1 to 9.0.20, it is possible that the application will continue to use the socket after it has been closed. The error handling triggered in this case could cause the a pooled object to be placed in the pool twice. This could result in subsequent connections using the same object concurrently which could result in data being returned to the wrong use and/or other errors.
| Релиз | Статус | Примечание |
|---|---|---|
| bionic | ignored | end of standard support, was needs-triage |
| esm-apps/bionic | needs-triage | |
| esm-infra/xenial | needs-triage | |
| upstream | needs-triage |
Показывать по
| Релиз | Статус | Примечание |
|---|---|---|
| bionic | ignored | end of standard support, was needs-triage |
| devel | not-affected | |
| esm-apps/bionic | needs-triage | |
| esm-apps/focal | not-affected | 9.0.31-1ubuntu0.2 |
| esm-apps/jammy | not-affected | |
| esm-apps/noble | not-affected | |
| focal | not-affected | 9.0.31-1ubuntu0.2 |
| impish | not-affected | |
| jammy | not-affected | |
| kinetic | not-affected |
Показывать по
Ссылки на источники
7.5 High
CVSS2
8.6 High
CVSS3
Связанные уязвимости
If a web application sends a WebSocket message concurrently with the WebSocket connection closing when running on Apache Tomcat 8.5.0 to 8.5.75 or Apache Tomcat 9.0.0.M1 to 9.0.20, it is possible that the application will continue to use the socket after it has been closed. The error handling triggered in this case could cause the a pooled object to be placed in the pool twice. This could result in subsequent connections using the same object concurrently which could result in data being returned to the wrong use and/or other errors.
If a web application sends a WebSocket message concurrently with the WebSocket connection closing when running on Apache Tomcat 8.5.0 to 8.5.75 or Apache Tomcat 9.0.0.M1 to 9.0.20, it is possible that the application will continue to use the socket after it has been closed. The error handling triggered in this case could cause the a pooled object to be placed in the pool twice. This could result in subsequent connections using the same object concurrently which could result in data being returned to the wrong use and/or other errors.
If a web application sends a WebSocket message concurrently with the W ...
Уязвимость сервера приложений Apache Tomcat, связанная с ошибками при одновременном закрытии соединения WebSocket и отправки сообщения WebSocket, позволяющая нарушителю раскрыть защищаемую информацию или оказать другое воздействие
7.5 High
CVSS2
8.6 High
CVSS3