OpenRemote vulnerabilities

OpenRemote notification deletion endpoints fail to enforce realm boundaries, allowing any realm administrator to delete notifications belonging to other realms. Attackers with write:admin role in one realm can send DELETE requests to remove notifications from the master realm or other tenants without authorization checks.

OpenRemote before 1.26.2 contains an authentication bypass vulnerability in the console registration API that allows unauthenticated attackers to update existing console assets by supplying a known asset identifier.

OpenRemote before version 1.28.0 contains a cross-realm information disclosure vulnerability in the Notification REST API. Tenant administrators can read all tenants' sent notifications including message bodies by submitting a zero-parameter GET request to the notification endpoint.

OpenRemote (org.openremote:openremote) versions up to 1.26.2 contain an insecure direct object reference (IDOR) vulnerability in the setAssetLinks endpoint of AlarmResourceImpl. The realm access check validates only a single realm obtained via realms.stream().findFirst() on a HashSet of realms from the request, rather than all realms. Due to non-deterministic HashSet iteration order, an authenticated attacker can, with roughly 50% probability per request (retryable), persist cross-tenant links and disclose victim asset names.

Vulnerability in OpenRemote before version 1.26.2. The SyslogResource REST endpoint (`GET /api/{realm}/syslog/event`) fails to filter operational logs by realm, allowing attackers with `read:rules` role to read logs from all tenants, including asset IDs, agent connection details, rule names, and protocol errors.

OpenRemote before version 1.26.0 contains an authenticated SQL injection vulnerability in the datapoint crosstab export endpoint. The vulnerability is caused by concatenating asset display names directly into PostgreSQL queries, allowing an attacker with asset creation or rename permissions to inject malicious SQL.

An IDOR vulnerability in OpenRemote before 1.25.0 allows authenticated users to permanently delete alarms belonging to other tenants by supplying arbitrary alarm IDs. The removeAlarms() method in AlarmResourceImpl.java omits realm-scoping validation in its JPA query.