GHSA-wwgf-3xp7-cxj4 – gos/web-socket-bundle

Package

Manager: composer
Name: gos/web-socket-bundle
Vulnerable Version: >=0 <1.10.4 || >=2.0.0 <2.6.1 || >=3.0.0 <3.3.0

Severity

Level: Medium

CVSS v3.1: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

CVSS v4.0: CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

EPSS: N/A pctlN/A

Details

Potentially sensitive data exposure in Symfony Web Socket Bundle ### Impact Inside `Gos\Bundle\WebSocketBundle\Server\App\Dispatcher\TopicDispatcher::onPublish()`, messages are arbitrarily broadcasted to the related Topic if `Gos\Bundle\WebSocketBundle\Server\App\Dispatcher\TopicDispatcher::dispatch()` does not succeed. The `dispatch()` method can be considered to not succeed if (depending on the version of the bundle) the callback defined on a topic route is misconfigured, a `Gos\Bundle\WebSocketBundle\Topic\TopicInterface` implementation is not found for the callback, a topic which also implements `Gos\Bundle\WebSocketBundle\Topic\SecuredTopicInterface` rejects the connection, or an Exception is unhandled. This can result in an unintended broadcast to the websocket server potentially with data that should be considered sensitive. ### Patches In 1.10.4, 2.6.1, and 3.3.0, `Gos\Bundle\WebSocketBundle\Server\App\Dispatcher\TopicDispatcher::onPublish()` has been changed to no longer broadcast an event's data if `Gos\Bundle\WebSocketBundle\Server\App\Dispatcher\TopicDispatcher::dispatch()` fails. ### Workarounds Upgrade to 1.10.4, 2.6.1, and 3.3.0 Note, the 1.x branch is considered end of support as of July 1, 2020. ### For more information If you have any questions or comments about this advisory: * Open an issue in [this repository](https://github.com/GeniusesOfSymfony/WebSocketBundle)

Metadata

Created: 2020-07-07T16:33:45Z
Modified: 2021-09-22T20:22:02Z
Source: https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2020/07/GHSA-wwgf-3xp7-cxj4/GHSA-wwgf-3xp7-cxj4.json
CWE IDs: ["CWE-200"]
Alternative ID: N/A
Finding: F017
Auto approve: 1