Comparison Overview
Sparkasse Siegen

Sparkasse Siegen
Morleystraße 2, Siegen, 57072, DE
Last Update: 02/04/2026
𝐖𝐢𝐫 𝐥𝐞𝐛𝐞𝐧 𝐝𝐢𝐞 𝐑𝐞𝐠𝐢𝐨𝐧 Seit 1842 steht die Sparkasse Siegen für verantwortungsvolles, zukunftsorientiertes Handeln und Wirtschaften. Etwas mehr als 210.000 Menschen leben im Geschäftsgebiet der Sparkasse Siegen. Rund 125.000 von ihnen sind unsere Kunden....

Intesa Sanpaolo
Piazza San Carlo 156, Turin, TO, IT, 10121
Last Update: 02/04/2026
Intesa Sanpaolo è il maggior gruppo bancario in Italia con una significativa presenza internazionale. Il suo business model distintivo la rende leader a livello europeo nel Wealth Management, Protection & Advisory e ne caratterizza l’orientamento al digitale. I’impegno ...
Compliance Ranges Comparison

Sparkasse Siegen







Intesa Sanpaolo






Benchmark & Cyber Underwriting Signals
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for Sparkasse Siegen in 2026.
Incidents vs Banking Industry Avg (This Year)
Intesa Sanpaolo has 4.76% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - Sparkasse Siegen (X = Date, Y = Severity)
Sparkasse Siegen cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Intesa Sanpaolo (X = Date, Y = Severity)
Intesa Sanpaolo cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Sparkasse Siegen

Intesa Sanpaolo
FAQ
Latest Global CVEs
Deserialization of untrusted data in Microsoft Edge (Chromium-based) allows an unauthorized attacker to execute code over a network.
The Bluetooth BAP Broadcast Assistant GATT client in subsys/bluetooth/audio/bap_broadcast_assistant.c reassembled remote Broadcast Receive State data into a single file-static net_buf_simple (att_buf, BT_ATT_MAX_ATTRIBUTE_LEN = 512 bytes) shared by all connection instances, while the BUSY flag, long-read handle, and reset/offset state were per-connection. When the device acts as a Broadcast Assistant connected to multiple Scan Delegator peripherals, notification and long-read callbacks from different connections interleave on the shared buffer: the append in notify_handler (net_buf_simple_add_mem at the not-busy branch) performs no tailroom check, so receive-state notifications from two or more delegators accumulate on the same 512-byte buffer and, with a sufficiently large configured ATT MTU (BT_L2CAP_TX_MTU up to 2000) and two-to-three concurrent connections, write past the buffer into adjacent .bss (net_buf_simple_add only asserts in debug builds). Even below the overflow threshold, one connection's net_buf_simple_reset zeroes the shared length while another connection's reassembly and GATT read offset are in flight, mixing one peer's data into another's parse. A malicious or compromised Scan Delegator (or two colluding peers) over BLE can trigger this, causing out-of-bounds writes (memory corruption / denial of service) and cross-connection data corruption. The fix moves the buffer into the per-connection instance struct so each connection reassembles into its own buffer. Affects Zephyr releases shipping the Broadcast Assistant with the shared buffer, including v4.4.0 and earlier.
ImageMagick before 7.1.2-26 contains a memory leak vulnerability in the VIFF encoder when memory allocation fails. Attackers can trigger allocation failures by processing specially crafted VIFF images to exhaust available memory and cause denial of service.
ImageMagick before 7.1.2-26 contains a use-after-free vulnerability in the FormatMagickCaption method when memory allocation fails. Attackers can trigger memory allocation failures to cause a dangling pointer to reference freed memory, potentially enabling denial of service or code execution.
ImageMagick before 7.1.2-26 contains a policy bypass vulnerability in the APNG encoder and external delegates due to missing validation checks. Attackers can write files to disallowed paths by bypassing configured policy restrictions through the APNG encoding process.