Comparison Overview
Baker Tilly Azerbaijan

Baker Tilly Azerbaijan
ул. Джалила Мамедгулузаде 102А., Баку, Насиминский район, AZ1022, AZ
Last Update: 21/02/2026
Baker Tilly Azerbaijan is an independent member of Baker Tilly International, a worldwide network of independent accounting and business advisory firms in 146 territories, with 36,000 professionals. The combined worldwide revenue of independent member firms is $3.9 bill...

Allianz
Koeniginstrasse 28, Munich, 80802, DE
Last Update: 13/05/2026
The Allianz Group is one of the world's leading insurers and asset managers with more than 100 million private and corporate customers in nearly 70 countries. We are proud to be the Worldwide Insurance Partner of the Olympic & Paralympic Movements from 2021 until 2032 a...
Compliance Ranges Comparison

Baker Tilly Azerbaijan







Allianz






Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Baker Tilly Azerbaijan in 2026.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Allianz in 2026.
Incident History - Baker Tilly Azerbaijan (X = Date, Y = Severity)
Baker Tilly Azerbaijan cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Allianz (X = Date, Y = Severity)
Allianz cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Baker Tilly Azerbaijan

Allianz
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.