Comparison Overview
Compensa Vienna Insurance Group ADB Latvijas filiāle

Compensa Vienna Insurance Group ADB Latvijas filiāle
Vienības gatve 87H, Rīga, undefined, LV-1004, LV
Last Update: 19/03/2026
Esam uzņēmums, kas vienmēr domā ilgtermiņā. Mūsu darbības pamatā ir godīgums un atklātība attiecībā pret katru sadarbības partneri un klientu. Compensa īpašnieka Vienna Insurance Group teju divsimt gadu ilgā pieredze apdrošināšanas tirgū ir pierādījums, ka ar savu attie...

Porto
Avenida Rio Branco, 1489, Sao Paulo, SP, BR, 01205-001
Last Update: 19/05/2026
A Porto é mais que uma seguradora, é um ecossistema de soluções de serviços de proteção com tecnologia embarcada, para melhorar e facilitar a experiência do cliente. Com mais de 70 anos de mercado, a atuação da companhia se concentra hoje em quatro pilares estratégicos ...
Compliance Ranges Comparison

Compensa Vienna Insurance Group ADB Latvijas filiāle







Porto






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

Compensa Vienna Insurance Group ADB Latvijas filiāle

Porto
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.