Mersive Solstice Pod

Solstice Pod API (version 5.5, 6.2) contains an unauthenticated API endpoint (`/api/config`) that exposes sensitive information such as the session key, server version, product details, and display name. Unauthorized users can extract live session information by accessing this endpoint without authentication.

Published: 2025-12-04T20:45:13.939Z
Updated: 2026-07-14T22:26:02.632Z

In Solstice Pod before 3.3.0 (or Open4.3), the Administrator password can be enumerated using brute-force attacks via the /Config/service/initModel?password= Solstice Open Control API because there is no complexity requirement (e.g., it might be all digits or all lowercase letters).

Published: 2020-12-23T14:58:20.000Z
Updated: 2024-08-04T17:09:13.971Z

In Solstice Pod before 3.3.0 (or Open4.3), the screen key can be enumerated using brute-force attacks via the /lookin/info Solstice Open Control API because there are only 1.7 million possibilities.

Published: 2020-12-23T14:56:11.000Z
Updated: 2024-08-04T17:09:14.132Z

In Solstice Pod before 3.0.3, the web services allow users to connect to them over unencrypted channels via the Browser Look-in feature. An attacker suitably positioned to view a legitimate user's network traffic could record and monitor their interactions with the web services and obtain any information the user supplies, including Administrator passwords and screen keys.

Published: 2020-12-23T14:53:19.000Z
Updated: 2024-08-04T17:09:14.640Z

Solstice-Pod up to 5.0.2 WEBRTC server mishandles the format-string specifiers %x; %p; %c and %s in the screen_key, display_name, browser_name, and operation_system parameter during the authentication process. This may crash the server and force Solstice-Pod to reboot, which leads to a denial of service.

Published: 2020-11-11T14:23:42.000Z
Updated: 2024-08-04T16:18:44.936Z