Comparison Overview
InterRisk Versicherungen - Vienna Insurance Group

InterRisk Versicherungen - Vienna Insurance Group
Carl-Bosch-Straße 5, Wiesbaden, 65203, DE
Last Update: 26/10/2025
Die beiden Unternehmen InterRisk Versicherungs-AG und InterRisk Lebensversicherungs-AG gehören zur Vienna Insurance Group. Die Vienna Insurance Group ist die führende Versicherungsgruppe in Österreich und eine der führenden Versicherungsgesellschaften in CEE. Die Ange...

Manulife
200 Bloor St E, Toronto, M4W, CA
Last Update: 28/04/2026
Manulife is a leading international financial services group that helps people make their decisions easier and lives better. With our global headquarters in Toronto, we operate as Manulife across our offices in Canada, Asia, and Europe, and primarily as John Hancock in ...
Compliance Ranges Comparison

InterRisk Versicherungen - Vienna Insurance Group







Manulife






Benchmark & Cyber Underwriting Signals
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for InterRisk Versicherungen - Vienna Insurance Group in 2026.
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for Manulife in 2026.
Incident History - InterRisk Versicherungen - Vienna Insurance Group (X = Date, Y = Severity)
InterRisk Versicherungen - Vienna Insurance Group cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Manulife (X = Date, Y = Severity)
Manulife cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

InterRisk Versicherungen - Vienna Insurance Group

Manulife
FAQ
Latest Global CVEs
An authenticated user with the read role may read limited amounts of uninitialized stack memory via specially-crafted issuances of the filemd5 command
The $_internalApplyOplogUpdate aggregation pipeline stage can be used to execute a document diff containing a malformed binary diff to return memory out-of-bounds or crash the server. $_internalApplyOplogUpdate can be executed by any authenticated user with access to the aggregate command.
An authorized user could trigger a server crash by running a query with a 2dsphere index on a field that stores a GeoJSON GeometryCollection containing a Polygon with a strict-winding CRS. Strict-winding polygons are intentionally unsupported for indexing, but the guard that rejects them does not inspect members of a GeometryCollection, allowing the unsafe path to be reached which ends with an ensuing null-pointer dereference.
The ldapQueryPassword parameter, when set through the runtime setParameter command, will log the new password to the mongod.log file in plain text.
An authenticated user can cause a MongoDB server to crash or return incorrect results by creating documents that interfere with internal metadata processing during query execution. This stems from insufficient separation between user-controlled document fields and internal metadata in certain execution paths.