Comparison Overview
Ipoteka bank OTP Group

Ipoteka bank OTP Group
Shahrisabz 30, Tashkent, Mirzo Ulugbek, UZ, 100000
Last Update: 18/12/2025
JSCMB Ipoteka bank OTP Group is the fifth largest bank in the banking system of Uzbekistan. The Bank accounts almost 7% of total assets and deposits in the banking system The bank serves more than 1.8 million corporate and retail clients through 39 branches and 212 cus...

Banco de Chile
Ahumada 251, Santiago, Santiago, 8320206, CL
Last Update: 02/04/2026
Somos una Corporación líder y comprometida con el país que brinda servicios financieros de excelencia a cada segmento de clientes. Buscamos permanentemente ser el mejor Banco para ellos, ser el mejor lugar para trabajar y ser la mejor inversión para nuestros accionistas...
Compliance Ranges Comparison

Ipoteka bank OTP Group







Banco de Chile






Benchmark & Cyber Underwriting Signals
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for Ipoteka bank OTP Group in 2026.
Incidents vs Banking Industry Avg (This Year)
No incidents recorded for Banco de Chile in 2026.
Incident History - Ipoteka bank OTP Group (X = Date, Y = Severity)
Ipoteka bank OTP Group cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Banco de Chile (X = Date, Y = Severity)
Banco de Chile cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Ipoteka bank OTP Group

Banco de Chile
FAQ
Latest Global CVEs
The GOOSE subscriber component improperly validates the UTC timestamp field in unauthenticated IEC 61850 GOOSE (EtherType 0x88B8) Layer-2 multicast messages. A specially crafted GOOSE frame containing an undersized timestamp field can trigger a heap out-of-bounds read during message processing, causing the process to crash and resulting in a denial-of-service condition.
OpenClaw Dashboard contains a stored cross-site scripting vulnerability that allows unauthenticated remote attackers to execute arbitrary JavaScript in the administrator's browser session by injecting HTML markup into agent transcript messages processed through the sessions API. Attackers can craft a message containing inline event handler payloads such as an img tag with an onerror attribute within the 60-character rendering budget, which is stored in the session transcript and interpolated unsanitized into innerHTML on the default landing page, allowing theft of session tokens and unauthorized calls to authenticated administrative endpoints including agent instruction file modification.
MeshCentral 1.1.21 contains a cross-site WebSocket hijacking protection bypass vulnerability that allows unauthenticated remote attackers to hijack authenticated administrator sessions by exploiting an unconditional early return in the CheckWebServerOriginName() function within webserver.js when self-signed certificates are in use. Attackers can open cross-origin WebSocket connections to any of the twelve WebSocket endpoints, send crafted action commands to exfiltrate the server sessionKey used to sign session cookies, forge session tokens as arbitrary users, and gain full remote control of all managed devices governed by the MeshCentral instance.
The GOOSE parser contains an off-by-one boundary-handling flaw that can be triggered by a single unauthenticated Layer-2 multicast frame on the process bus. When specific GOOSE message fields are processed, the parser advances its internal buffer position incorrectly, resulting in a heap out-of-bounds read. On affected platforms, this condition reliably terminates the subscriber process and causes a denial-of-service.
The GOOSE payload parser contains a boundary handling flaw that can be triggered by a single unauthenticated Layer 2 multicast frame on the process bus. When processing specific payload fields, an attacker controlled inner element length may exceed its enclosing length, causing the parser to over read by one byte. This out-of-bounds read reliably terminates the subscriber process, resulting in a denial-of-service condition.