Comparison Overview
metafinanz Informationssysteme GmbH

metafinanz Informationssysteme GmbH
Leopoldstraße 146, Munich, 80804, DE
Last Update: 31/03/2026
For over 35 years, metafinanz Informationssysteme GmbH, a business and IT consulting company, has been at the side of its customers in an increasingly digital and dynamic world. Our promise: We shine a new light on future viability. We enable our customers to find, deve...

LTIMindtree
L&T Infotech, Technology Tower. Gate No. 5, Saki Vihar Road, Powai, Mumbai, Maharashtra 400072, IN, Mumbai, MH, IN, 400072
Last Update: 05/04/2026
LTIMindtree is a global technology consulting and digital solutions company that partners with enterprises across industries to reimagine business models, accelerate innovation, and drive AI-centric growth. Trusted by more than 700 clients worldwide, we use advanced tec...
Compliance Ranges Comparison

metafinanz Informationssysteme GmbH







LTIMindtree






Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for metafinanz Informationssysteme GmbH in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for LTIMindtree in 2026.
Incident History - metafinanz Informationssysteme GmbH (X = Date, Y = Severity)
metafinanz Informationssysteme GmbH cyber incidents detection timeline including parent company and subsidiaries.
Incident History - LTIMindtree (X = Date, Y = Severity)
LTIMindtree cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

metafinanz Informationssysteme GmbH

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