Know every vulnerabilitybefore it knows you.
DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.
GHSA-h3m5-97jq-qjrf
No affected components available
Summary
OpenRemote Manager is vulnerable to a cross-tenant Insecure Direct Object Reference (IDOR) in the bulk alarm deletion endpoint. An authenticated user in any realm can delete alarms belonging to other realms (tenants) by supplying arbitrary alarm IDs. The vulnerability exists because the bulk removeAlarms() method only verifies that the caller's own realm is active and accessible, but never checks whether the targeted alarm IDs belong to the caller's realm before deleting them.
This allows any user with alarm write permissions in their own realm to permanently destroy alarm records — including safety-critical and security alerts — belonging to any other tenant on the same OpenRemote installation.
[Additional Information] The singular removeAlarm() method correctly validates that the target alarm's realm matches the caller's access:
// CORRECT (singular):
SentAlarm alarm = alarmService.getAlarm(alarmId);
if (!isRealmActiveAndAccessible(alarm.getRealm())) {
throw new ForbiddenException(...);
}
The plural removeAlarms() method is missing this per-alarm realm check and only validates the caller's own realm — a check that is trivially satisfied for any authenticated user:
// VULNERABLE (plural):
public void removeAlarms(RequestParams requestParams, List<Long> alarmIds) {
if (!isRealmActiveAndAccessible(getAuthenticatedRealmName())) {
throw new ForbiddenException(...); // always passes for any auth user
}
List<SentAlarm> alarms = alarmService.getAlarms(alarmIds); // no realm filter
alarmService.removeAlarms(alarms, alarmIds); // no realm filter
}
The underlying service queries contain no realm scoping:
// AlarmService.getAlarms(List<Long>):
"select sa from SentAlarm sa where sa.id in :ids"
// no realm filter
// AlarmService.removeAlarms():
"delete from SentAlarm sa where sa.id in :ids"
// no realm filter
Alarm IDs are sequential auto-increment Long values (JPA @GeneratedValue), making them trivially enumerable.
[Vulnerability Type] Insecure Direct Object Reference (IDOR) / Missing Authorization CWE-639: Authorization Bypass Through User-Controlled Key CWE-862: Missing Authorization
[Vendor of Product] OpenRemote Inc. (openremote.io)
[Affected Product Code Base] OpenRemote Manager - current version as of 2026 (github.com/openremote/openremote)
[Affected Component] org.openremote.manager.alarm.AlarmResourceImpl#removeAlarms() org.openremote.manager.alarm.AlarmService#getAlarms(List<Long>) org.openremote.manager.alarm.AlarmService#removeAlarms()
File: manager/src/main/java/org/openremote/manager/alarm/AlarmResourceImpl.java File: manager/src/main/java/org/openremote/manager/alarm/AlarmService.java
[Attack Type] Remote (authenticated)
[CVE Impact Other] Cross-tenant permanent destruction of alarm records, including safety-critical and security alerts in IoT environments. Also enables cross-tenant alarm enumeration (presence disclosure of alarm IDs across all tenants).
[Attack Vectors]
- Attacker registers or obtains any low-privilege account in any realm on the target OpenRemote installation (or uses an existing account).
- Attacker enumerates alarm IDs belonging to other realms by sending bulk delete requests with sequential IDs (presence confirmed by 404 vs 200 response codes).
- Attacker issues a single bulk delete request containing IDs of alarms belonging to victim realm(s).
- Alarms are permanently deleted with no authorization error.
PoC:
Tenant A (attacker) : realm = "tenant-a"
user = attacker@tenant-a.com
role = WRITE_ALARMS_ROLE
Tenant B (victim) : realm = "tenant-b"
alarms with IDs 1174,1173, 1180 exist
DELETE /api/smartcity/alarm HTTP/2
Content-Type: application/json
[1174,1173, 1180] /// <- alarm ID
<img width="1280" height="404" alt="image" src="https://github.com/user-attachments/assets/ffbebea2-2248-42a0-bb22-7a0dc51c78ce" />The vulnerability can be exploited over the network without needing physical access. It is easy for an attacker to exploit this vulnerability. An attacker needs basic access or low-level privileges. No user interaction is needed for the attacker to exploit this vulnerability. The vulnerability can affect other systems as well, not just the initial system. There is a high impact on the integrity of the data. There is a high impact on the availability of the system.
Exploitation activity has been observed. Apply available patches or mitigations urgently.
The exploit probability is very low. The vulnerability is unlikely to be exploited in the next 30 days.
We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.
Browse More
Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.
Checkout DevGuard