Rocket.Chat Workspace Exposure Starts With Role and Token Authority
Rocket.Chat Workspace Exposure Starts With Role and Token Authority Rocket.Chat is more than a chat page. A workspace contains user identities, rooms, OAuth applications, API access, and administrative settings. Discov
Rocket.Chat Workspace Exposure Starts With Role and Token Authority
Rocket.Chat is more than a chat page. A workspace contains user identities, rooms, OAuth applications, API access, and administrative settings. Discovering an exposed instance is useful only when the review follows those authority paths.
What the count shows
On 2026-11-20, a ZoomEye SDK query with sub_type=all, page 1, and pagesize 1 returned 2,168 matches for app="Rocket.Chat" and 24,568 for title="Rocket.Chat". The title count is broad and can include unrelated pages. The application fingerprint is a narrower starting point, but neither number proves that any instance is vulnerable or misconfigured.
Security model
Rocket.Chat uses roles and granular permissions. A moderator role has room-scoped effects, while workspace permissions control global actions. Its authentication options include LDAP, SAML, OAuth, and OpenID Connect, and users can create personal access tokens when policy allows.
That produces several review questions: who can create OAuth apps, who can synchronize users, who can change settings, and who can issue or revoke API tokens. A workspace with strong login but broad token creation has a different risk profile from one with restrictive role assignments.
Inventory and triage
Use the application-fingerprint results to build an owner list. Confirm the product version from the server rather than from the page title. Record the external URL, tenant or organization, authentication method, and whether registration is open.
For prioritized instances, review administrative roles, integrations, incoming and outgoing webhooks, and OAuth service permissions. Check whether old user accounts still have tokens and whether disabled users retain role assignments.
Monitoring workflow
Track changes to roles, token creation policy, identity-provider configuration, and administrative users. Alert on new OAuth applications and on users gaining workspace administration after an external identity change.
ZoomEye provides the public discovery layer. Internal evidence must establish whether the workspace is expected, who owns it, and whether its authorization settings match policy. A public login page is an inventory lead, not a compromise finding.
References
Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes β full credit and traffic to the original publisher.