Comparison Overview
PT Bank Danamon Indonesia Tbk

PT Bank Danamon Indonesia Tbk
Jl. HR. Rasuna Said Blok C No. 10, Karet Setiabudi, JAKARTA, DKI Jakarta, ID, 12940
Last Update: 15/09/2026
PT Bank Danamon Indonesia Tbk (BEI: BDMN) didirikan pada tahun 1956. Per 31 Desember 2024, Danamon mengelola aset konsolidasian sebesar Rp242 triliun dengan anak perusahannya, Adira Finance. Dalam hal kepemilikan saham, 92,47% saham Danamon dimiliki oleh MUFG, dan 7,53%...

Banco Azteca
Av. Insurgentes Sur 3579, México, 14020, MX
Last Update: 15/09/2026
Banco Azteca es un banco mexicano fundado en el año 2002 y es una compañía de Grupo Salinas del empresario Mexicano Ricardo Salinas Pliego. Cuenta con 1,500 sucursales en México, Panamá, Argentina, Honduras, El Salvador, Brasil y Perú; es uno de los dos bancos más grand...
Compliance Ranges Comparison

PT Bank Danamon Indonesia Tbk







Banco Azteca






Benchmark & Cyber Underwriting Signals
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for PT Bank Danamon Indonesia Tbk in 2026.
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for Banco Azteca in 2026.
Incident History - PT Bank Danamon Indonesia Tbk (X = Date, Y = Severity)
PT Bank Danamon Indonesia Tbk cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Banco Azteca (X = Date, Y = Severity)
Banco Azteca cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

PT Bank Danamon Indonesia Tbk

Banco Azteca
FAQ
Latest Global CVEs
A security flaw has been discovered in THU-MIG yoloe up to 40cd606cabdbe2b566d6f14a6b162c89206e9a1b. This affects the function eval of the file ultralytics/nn/autobackend.py of the component AutoBackend Model Loading. The manipulation of the argument imgsz/names/kpt_shape results in improper neutralization of directives in dynamically evaluated code. The attack requires a local approach. The exploit has been released to the public and may be used for attacks. This product does not use versioning. This is why information about affected and unaffected releases are unavailable. The project was informed of the problem early through an issue report but has not responded yet.
Coder before 2.34.7 contains an IP spoofing vulnerability in the ExtractRealIPAddress middleware that trusts the leftmost, client-supplied X-Forwarded-For value instead of the client IP appended by a reverse proxy. Attackers can send forged X-Forwarded-For values through appending proxies to bypass per-IP rate limits on login, one-time passcode, and password validation endpoints, enabling brute-force attacks, and to falsify IP addresses recorded in audit logs.
Coder before 2.29.17, 2.30.0 before 2.32.7, 2.33.0 before 2.33.8, and 2.34.0 before 2.34.2 contains a user enumeration vulnerability because userpassword.Compare() substitutes a placeholder hash derived from the string "hunter2" when a stored password hash is empty. Unauthenticated attackers can submit logins with the password "hunter2" and distinguish HTTP 403 from 401 responses to enumerate valid accounts and reveal the authentication provider of SSO-only users.
Coder before 2.29.17, 2.30.0 before 2.32.7, 2.33.0 before 2.33.8, and 2.34.0 before 2.34.2 contains a stored HTML injection vulnerability because the ApplicationName and LogoURL appearance settings are rendered into HTML output without sufficient escaping. Attackers with the Owner role can store HTML markup in these settings that renders in the Coder dashboard and in SMTP notification emails sent to other deployment users.
Coder from 2.0.0 before 2.34.8 contains an open redirect vulnerability in handleAPIKeySmuggling that allows attackers to redirect users externally via unsanitized r.URL.Path values. Attackers can craft links on trusted workspace app subdomains with paths beginning with double slashes, which become scheme-relative redirects to attacker sites for phishing.