Comparison Overview
LexCom Informationssysteme GmbH

LexCom Informationssysteme GmbH
Rüdesheimerstr. 23, München, 80686, DE
Last Update: 01/04/2026
LexCom zählt weltweit zu den führenden Anbietern von Informations-, Kommunikations- und Vertriebssystemen im After Sales Bereich. Seit über 40 Jahren sind wir erfolgreich tätig, insbesondere für Hersteller, Händler und Servicepartner in der Automobilbranche.Mehr als 2...

Accenture in India
IBC Knowledge Park,, Bengaluru, 560029, IN
Last Update: 01/04/2026
Accenture is a global professional services company with leading capabilities in digital, cloud and security. Combining unmatched experience and specialized skills across more than 40 industries, we offer Strategy and Consulting, Interactive, Technology and Operations s...
Compliance Ranges Comparison

LexCom Informationssysteme GmbH







Accenture in India






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

LexCom Informationssysteme GmbH

Accenture in India
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.