Comparison Overview
La Caja de Ahorro y Seguro

La Caja de Ahorro y Seguro
Fitz Roy 957, Ciudad Autónoma de Buenos Aires, 1414, AR
Last Update: 03/04/2026
La Caja es la compañía de seguros líder de Argentina. Con una marcada orientación hacia la tecnología y la innovación, se destaca por su variada oferta de productos que busca satisfacer las necesidades de los clientes de la forma más simple. Cuenta con seguros para Auto...

Liberty Mutual Insurance
175 Berkeley Street, Boston, 02116, US
Last Update: 21/05/2026
At Liberty Mutual, we believe progress happens when people feel secure. For more than 110 years we have helped people and businesses embrace today and confidently pursue tomorrow by providing protection for the unexpected and delivering it with care. A Fortune 100 c...
Compliance Ranges Comparison

La Caja de Ahorro y Seguro







Liberty Mutual Insurance






Benchmark & Cyber Underwriting Signals
Incidents vs Insurance Industry Avg (This Year)
No incidents recorded for La Caja de Ahorro y Seguro in 2026.
Incidents vs Insurance Industry Avg (This Year)
Liberty Mutual Insurance has 7.41% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - La Caja de Ahorro y Seguro (X = Date, Y = Severity)
La Caja de Ahorro y Seguro cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Liberty Mutual Insurance (X = Date, Y = Severity)
Liberty Mutual Insurance cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

La Caja de Ahorro y Seguro

Liberty Mutual Insurance
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.