EtherCalc exposure begins with the room model
EtherCalc is a collaborative spreadsheet that can create a workbook directly from a URL. The product also exposes a REST API and deployment settings that control room creation and room discovery. A title count should lead to those controls, not to a claim about exposed data.
Measurement
ZoomEye returned 835 matches for title="EtherCalc" with sub_type=all, page 1, and page size 1 at 2026-11-21T02:48:02+08:00. The application query app="EtherCalc" succeeded with zero matches.
The title can appear on public workbooks, project pages, docs, and self-hosted instances. It is not evidence that a room is readable or writable.
Identify the access model
The repository API documentation describes room creation and access behavior, including optional authentication settings. The deployment may configure WebAuthn trust anchors, a room-create limit, and controls that hide the room index. Those are different layers:
- Whether a client can create a room.
- Whether a client can discover room names.
- Whether a client can read or write a known room.
- Whether an export or API route is available.
Test each layer separately. A hidden room index reduces discoverability. It does not authenticate a known room URL. A room creation limit reduces abuse. It does not protect an existing workbook.
Check the reverse proxy and app together
If the service is placed behind SSO or basic authentication, verify that the WebSocket and REST paths use the same protection. Browser clients often make a page request and then open a real-time channel. Protecting only the first request creates a gap.
Review X-Forwarded-* or platform edge headers when the application uses them for room limits or access decisions. The edge should overwrite untrusted values. The application should not trust a client-supplied source identity.
Review import and export
Spreadsheets may accept imported files, formulas, or external links. Validate file type and size, disable external fetch where not needed, and sanitize exported content. Formula injection and data exfiltration are separate from room access, but they affect the same user data.
Backups should follow the workbook retention policy. A room deleted from the UI may remain in a snapshot, object store, or cache. Record the deletion path and the storage owner.
Turn the count into a control matrix
Group the 835 title matches by domain. Confirm which are actual spreadsheet deployments. For each one, document room creation, directory visibility, known-room access, API behavior, proxy authentication, retention, and export controls.
The title count is useful for finding candidates. The room model and proxy boundary decide what an outside visitor can do.
Top comments (0)