| Package | Affected versions | Patched versions |
|---|---|---|
| onionshare-cli | ≥ 2.3, < 2.5< 2.5 | 2.5 |
| onionshare | < 2.5 | 2.5 |
Between September 26, 2021 and October 8, 2021, Radically Open Security conducted a penetration test of OnionShare 2.4, funded by the Open Technology Fund's Red Team lab. This is an issue from that penetration test.
Anyone with access to the chat environment can write messages disguised as another chat participant.
Prerequisites:
This screenshot shows Alice (glimpse-depress) and Bob (blinker-doorpost) joined a chatroom and are the only participants in the chatroom. Then the non-listed user squad-nursing writes a message in the chatroom without being visible in the list of users. The sending of the message itself is not required but was done here to show the initial access. The non-listed participant now renames himself to Bob and writes another message, seemingly coming from Bob.
This can be reproduced by slightly modifying the client-side JavaScript. The joined emit needs to be removed from the socket.on(connect) event handler. Therefore a client is not listed in the userlist and has no active session.
This can be done either via a crafted client or runtime modification of the chat.js script in the browser's internal debugger.
It is still possible to call the text method and send text to the chat via websocket.
It is also possible to call the update_username function and choose an existing username from the chat.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site freeAfterwards the hidden user can send messages that are displayed as coming from the impersonated user. There is no way to distinguish between the fake and original message.
An adversary with access to the chat environment can impersonate existing chat participants and write messages but not read the conversation. The similar exploit described in OTF-004 (page 19) has only slightly more requirements but also allows for reading.