Comparison Overview
Xact by Rambøll

Xact by Rambøll
Olof Palmes Allé 20, Aarhus N, 8200, DK
Last Update: 27/11/2025
Xact by Rambøll is a Scandinavian market leader in quantitative data collection. Every year our customers use SurveyXact to send out more than 100.000 surveys to more than 10.000.000 respondents. That is approximately one survey every 5 minutes. Xact by Rambøll is a f...

Iron Mountain
33 Arch St, Boston, 02110, US
Last Update: 07/05/2026
In the era of AI, your data is your advantage. Yet too often it remains untapped: disconnected from systems, underutilized, untrained, and exposed to risk. Iron Mountain is the trusted partner for organizations of all sizes to unlock what’s possible, transforming inform...
Compliance Ranges Comparison

Xact by Rambøll







Iron Mountain






Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Xact by Rambøll in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Iron Mountain in 2026.
Incident History - Xact by Rambøll (X = Date, Y = Severity)
Xact by Rambøll cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Iron Mountain (X = Date, Y = Severity)
Iron Mountain cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Xact by Rambøll

Iron Mountain
FAQ
Latest Global CVEs
The CONS_HISTORY ioctl handler did not adequately validate the requested history size. A large value caused an integer overflow in the buffer size calculation, resulting in a heap allocation smaller than expected. Subsequent initialization of the buffer wrote beyond the end of the allocation. An unprivileged local user with access to a vt(4) device can trigger an out-of-bounds write in the kernel, potentially escalating privileges.
The ELF image activator cleared per-process ASLR preference flags for setuid binaries after the code that computes the PIE base address, rather than before. As a result, a user-requested ASLR disable was still in effect at the point where the base address was chosen. An unprivileged local user can disable ASLR for a setuid PIE binary by calling procctl(2) before execve(2). This makes exploitation of any separate memory corruption vulnerability in that binary significantly easier.
Second, the audio buffer backing a mapping could be freed when the device was closed even though the mapping remained valid. The freed memory could then be reused elsewhere while still accessible through the stale mapping. The /dev/dsp device nodes are world-accessible by default. On a system with an audio device, either issue allows an unprivileged local user to read and write kernel memory, which can be used to escalate privileges, potentially gaining full control of the affected system. At a minimum, an attacker can crash the kernel, resulting in a Denial of Service (DoS).
The Linuxulator determined whether a binary was set-user-ID or set-group-ID by checking the P_SUGID process flag. During execve(2), this flag is not yet set at the point where the auxiliary vector is constructed, so AT_SECURE was incorrectly set to zero for set-user-ID and set-group-ID executables. An unprivileged local user can inject a shared library via LD_PRELOAD into a set-user-ID or set-group-ID Linux binary, gaining the privileges of that binary.
The kernel handler for IPV6_MSFILTER dropped a serializing lock in order to copy the source-filter list from userspace, then reacquired the lock. During this window another thread could free the multicast filter structure, leaving the handler with a stale pointer to freed memory. An unprivileged local user can exploit this use-after-free to escalate privileges.