Comparison Overview
Islamic Development Bank (IsDB)

Islamic Development Bank (IsDB)
8111 King Khalid St. AI Nuzlah AI Yamania Dist., Unit No. 1, Jeddah, Jeddah 22332-2444, SA, 8111
Last Update: 13/02/2026
The Islamic Development Bank (IsDB) Group is a global multilateral financial development institution established in 1975 to foster economic growth and inspire social progress among its 57 member countries and Muslim communities worldwide. Originality and Solidarity for...

COTO
Ciudad Autónoma de Buenos Aires, AR
Last Update: 14/09/2026
¿Sabés lo importante que es para nosotros que formes parte de COTO? Te proponemos superarte con proyectos arquitectónicos increíbles como, por ejemplo, la construcción de un mega centro comercial, o profesionalizarte en Comercio Exterior interactuando con los mercados ...
Compliance Ranges Comparison

Islamic Development Bank (IsDB)







COTO






Benchmark & Cyber Underwriting Signals
Incidents vs International Trade and Development Industry Avg (This Year)
No incidents recorded for Islamic Development Bank (IsDB) in 2026.
Incidents vs International Trade and Development Industry Avg (This Year)
No incidents recorded for COTO in 2026.
Incident History - Islamic Development Bank (IsDB) (X = Date, Y = Severity)
Islamic Development Bank (IsDB) cyber incidents detection timeline including parent company and subsidiaries.
Incident History - COTO (X = Date, Y = Severity)
COTO cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Islamic Development Bank (IsDB)

COTO
FAQ
Latest Global CVEs
A flaw was found in nfs-utils. An unauthenticated remote attacker can trigger a Denial of Service (DoS) by sending repeated state notification requests to an exposed rpc.statd service. The service fails to properly release memory allocated during callback processing, leading to continuous memory growth. Sustained requests can exhaust system resources, eventually causing the service to degrade or crash.
A flaw was found in parted. A heap-based buffer overflow exists in libparted's file system resizing logic when handling FAT16 volumes. By convincing a user or administrator to resize a specially crafted FAT16 file system image with malformed directory metadata, an attacker can trigger an oversized read into a fixed-size memory buffer. This issue causes memory corruption, resulting in an application crash and a denial of service (DoS).
A flaw was found in parted. A heap-based buffer overflow can occur when processing a specially crafted FAT32 filesystem due to an integer calculation error during buffer allocation. A local attacker could exploit this by enticing a user or automated service to open a malicious filesystem image, resulting in an application crash leading to a Denial of Service (DoS) or potential memory corruption.
A flaw was found in libarchive. An attacker can cause a Denial of Service (DoS) or potential information disclosure due to a use-after-free vulnerability, which occurs when a program reads memory that has already been released. This issue arises when the archive_entry_copy_mac_metadata() function deallocates an internal buffer before completing a data copy. An attacker who can supply input to an application utilizing this function can trigger the flaw to crash the application or read uninitialized memory data.
A flaw was found in Nautilus. When a removable drive or disk image is unmounted or ejected, Nautilus prompts the user to empty the trash without verifying whether the trash directory paths are symbolic links. An attacker can exploit this flaw by tricking a user into mounting a crafted storage volume and confirming the prompt to empty the trash, leading to the arbitrary deletion of files accessible to that user.