Comparison Overview
Morningstar Sustainalytics

Morningstar Sustainalytics
De Entree 83, Amsterdam, undefined, 1100AB, NL
Last Update: 05/03/2026
Morningstar Sustainalytics is a leading independent ESG and corporate governance research, ratings and analytics firm that supports investors around the world with the development and implementation of responsible investment strategies. For 30 years, the firm has been a...

IIFL (India Infoline Group)
B Wing, Trade Centre, Kamala Mills Compound, Lower Parel, Off Senapati Bapat Marg,, Mumbai, Maharashtra, IN, 400013
Last Update: 02/04/2026
IIFL group is one of India's largest diversified financial services conglomerates with three listed entities - IIFL Finance, IIFL Securities and 360 ONE Wealth & Asset Management. Founded in 1995 by Nirmal Jain as a small research house, today IIFL Group employs over 40...
Compliance Ranges Comparison

Morningstar Sustainalytics







IIFL (India Infoline Group)






Benchmark & Cyber Underwriting Signals
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for Morningstar Sustainalytics in 2026.
Incidents vs Financial Services Industry Avg (This Year)
No incidents recorded for IIFL (India Infoline Group) in 2026.
Incident History - Morningstar Sustainalytics (X = Date, Y = Severity)
Morningstar Sustainalytics cyber incidents detection timeline including parent company and subsidiaries.
Incident History - IIFL (India Infoline Group) (X = Date, Y = Severity)
IIFL (India Infoline Group) cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Morningstar Sustainalytics

IIFL (India Infoline Group)
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.