The client in Tryton 5.x before 5.0.1 tries to make a connection to the bus in cleartext instead of encrypted under certain circumstances in bus.py and jsonrpc.py. This connection attempt fails, but it contains in the header the current session of the user. This session could then be stolen by a man-in-the-middle.
Authenticating a user, or otherwise establishing a new user session, without invalidating any existing session identifier gives an attacker the opportunity to steal authenticated sessions.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Tryton | Tryton | 5.0.0 (including) | 5.0.0 (including) |
| Tryton-client | Ubuntu | bionic | * |
| Tryton-client | Ubuntu | cosmic | * |
| Tryton-client | Ubuntu | disco | * |
| Tryton-client | Ubuntu | eoan | * |
| Tryton-client | Ubuntu | groovy | * |
| Tryton-client | Ubuntu | hirsute | * |
| Tryton-client | Ubuntu | impish | * |
| Tryton-client | Ubuntu | kinetic | * |
| Tryton-client | Ubuntu | lunar | * |
| Tryton-client | Ubuntu | mantic | * |
| Tryton-client | Ubuntu | trusty | * |
| Tryton-client | Ubuntu | xenial | * |
Such a scenario is commonly observed when: