Comparison Overview
Mercedes-Benz Research and Development India

Mercedes-Benz Research and Development India
Plot No - 5 - P, 1, Whitefield Main Road, near Sathya Sai Baba Hospital, EPIP Zone, Hoodi, Bangalore, 56066, IN
Last Update: 01/04/2026
Mercedes-Benz Research and Development India (MBRDI) is the largest research and development centre for Mercedes-Benz Group AG outside of Germany. With over 27 years of innovation, MBRDI is contributing towards building the world’s most desirable cars, right here from I...

Ferrari
Abetone inferiore, Maranello, 41053, IT
Last Update: 20/05/2026
Ferrari's story officially began in 1947 when its first road car, the 125 S, emerged from the gate of no. 4 Via Abetone Inferiore in Maranello. The iconic two-seater went on to win the Rome Grand Prix later that year and shortly thereafter was developed into a refined G...
Compliance Ranges Comparison

Mercedes-Benz Research and Development India







Ferrari






Benchmark & Cyber Underwriting Signals
Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)
No incidents recorded for Mercedes-Benz Research and Development India in 2026.
Incidents vs Motor Vehicle Manufacturing Industry Avg (This Year)
No incidents recorded for Ferrari in 2026.
Incident History - Mercedes-Benz Research and Development India (X = Date, Y = Severity)
Mercedes-Benz Research and Development India cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Ferrari (X = Date, Y = Severity)
Ferrari cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Mercedes-Benz Research and Development India

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