Comparison Overview
BBVA en Colombia

BBVA en Colombia
Cra. 9 # 72 - 35, Bogotá, 057, CO
Last Update: 20/03/2026
En BBVA te acompañamos para que alcances tus metas, alimentando tu confianza para que te sientas más capaz de decidir y avances con ilusión. Creemos en un modelo de relación corresponsable que te pone en el centro: nos movemos contigo, impulsando tus proyectos a través ...

Sicoob
SIG Quadra 6 Lote 2080, Brasília, DF, BR, 70610-460
Last Update: 29/05/2026
O Sicoob é o maior sistema financeiro cooperativo do país, com mais de 9 milhões de cooperados e mais de 4,6 mil pontos de atendimento distribuídos em todo o Brasil. Somos uma cooperativa financeira que oferece aos cooperados serviços de conta corrente, crédito, investi...
Compliance Ranges Comparison

BBVA en Colombia







Sicoob






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

BBVA en Colombia

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