Comparison Overview
Hiscox Assurances France

Hiscox Assurances France
49 avenue de l’Opéra, Paris, 75002, FR
Last Update: 19/12/2025
Fondé à Londres en 1901, Hiscox est un Groupe international qui réunit des sociétés dédiées à la souscription, au développement et à la vente de produits d'assurances spécialisés. Hiscox assure notamment plus de 10 000 particuliers dont 35% des 400 premières fortunes f...

AXA XL
One Bermudiana Road, Hamilton, Bermuda, BM, HM08
Last Update: 01/04/2026
We are a leading provider of insurance and reinsurance offering innovative risk management solutions for businesses worldwide. We partner with those who move the world forward, navigating complex risks and working across diverse industries to support and empower our cli...
Compliance Ranges Comparison

Hiscox Assurances France







AXA XL






Benchmark & Cyber Underwriting Signals
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for Hiscox Assurances France in 2026.
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for AXA XL in 2026.
Incident History - Hiscox Assurances France (X = Date, Y = Severity)
Hiscox Assurances France cyber incidents detection timeline including parent company and subsidiaries.
Incident History - AXA XL (X = Date, Y = Severity)
AXA XL cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Hiscox Assurances France

AXA XL
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.