Comparison Overview
Technische Unie Datacom & Smart Building

Technische Unie Datacom & Smart Building
Bovenkerkerweg 10, Amstelveen, NL
Last Update: 21/03/2026
De vraag naar data- en smart building oplossingen neemt toe zeker met de nieuwe wet en regelgeving in 2026. Technische Unie is een onafhankelijke partner om met u mee te denken over oplossingen, technische invulling en mogelijke slimme alternatieven op het gebied van da...

ID Logistics Group
55, Chemin des Engranauds, Orgon, 13660, FR
Last Update: 02/04/2026
ID Logistics, headed by Eric Hémar, is an international contract logistics group with revenues of €3.3 billion in 2024. ID Logistics manages nearly 450 sites in 19 countries, representing more than 9 million m² operated in Europe, America, Asia and Africa, with 42,000 e...
Compliance Ranges Comparison

Technische Unie Datacom & Smart Building







ID Logistics Group






Benchmark & Cyber Underwriting Signals
Incidents vs Transportation, Logistics, Supply Chain and Storage Industry Avg (This Year)
No incidents recorded for Technische Unie Datacom & Smart Building in 2026.
Incidents vs Transportation, Logistics, Supply Chain and Storage Industry Avg (This Year)
No incidents recorded for ID Logistics Group in 2026.
Incident History - Technische Unie Datacom & Smart Building (X = Date, Y = Severity)
Technische Unie Datacom & Smart Building cyber incidents detection timeline including parent company and subsidiaries.
Incident History - ID Logistics Group (X = Date, Y = Severity)
ID Logistics Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Technische Unie Datacom & Smart Building

ID Logistics Group
FAQ
Latest Global CVEs
In OpenStack Designate before 22.0.2, the mDNS handler performs pool-blind lookups when resolving record queries and NOTIFY requests. When two zones with the same name exist across different pools, the lookup fails with a deterministic error, causing the handler to return REFUSED for all DNS queries through that path. The _handle_notify path is exploitable via a single unauthenticated UDP packet. This is independently reachable through the cross-tenant zone overlap described in a different recent CVE, and also affects legitimate same-tenant cross-pool configurations. BIND9 views do not mitigate this issue as mDNS is a shared service upstream of any view configuration.
In OpenStack Designate before 22.0.1, zone creation checks (_is_subzone, _is_superzone, and the duplicate-zone DB constraint) are scoped to the target pool only. An authenticated user can bypass these checks by scheduling a zone to a different pool via the AttributeFilter scheduler, creating an overlapping zone that conflicts with another tenant's zone. This enables cross-tenant DNS hijack (redirecting traffic to attacker-controlled IPs) and DNS denial of service (NODATA responses). Exploitation requires a multi-pool deployment with AttributeFilter enabled in scheduler_filters, which is a non-default but documented and supported configuration for self-service tiering.
UpSnap is a wake on lan web app. Versions prior to 5.4.0 have an OS command injection vulnerability in the UpSnap’s device management functionality due to the presence of unsafe shell command template interpolation using the ip and the mac fields. User-controlled values can be inserted into the wake_cmd and shutdown_cmd templates and executed via /bin/sh -c (Linux) or cmd /C (Windows) without sanitization, resulting in an authenticated Remote Code Execution (RCE). A low-privileged user with permission to create or edit devices can execute arbitrary operating system commands on the UpSnap hosted server. Version 5.4.0 patches the issue.
FUXA is a web-based Process Visualization (SCADA/HMI/Dashboard) software. When `secureEnabled=true`, FUXA `1.3.0-2773` still allows guest and invalid-token requests to read project, alarms, and scheduler APIs. Version 1.3.1 fixes this issue.
FUXA is a web-based Process Visualization (SCADA/HMI/Dashboard) software. In fuxa-server version 1.3.0, the GET /api/project endpoint exposes sensitive project configuration data to guest-context requests even when secureEnabled is enabled. Version 1.3.1 fixes the issue.