Comparison Overview
Vodafone Tech Innovation Center Dresden

Vodafone Tech Innovation Center Dresden
Dresden, DE
Last Update: 06/03/2026
The Vodafone Tech Innovation Center Dresden is Vodafone’s new global center for innovation and co-creation with other top tech world-wide companies, universities and research institutes. The scope of this new hub is to improve peoples' lives by innovating communications...

Vodafone
1 Kingdom Street, Paddington Central, London, GB, W2 6BY
Last Update: 02/04/2026
At Vodafone, we believe that connectivity is a force for good. If we use it for the things that really matter, it can improve people's lives and the world around us. Through our technology we empower people, connecting everyone regardless of who they are or where they...
Compliance Ranges Comparison

Vodafone Tech Innovation Center Dresden







Vodafone






Benchmark & Cyber Underwriting Signals
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for Vodafone Tech Innovation Center Dresden in 2026.
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for Vodafone in 2026.
Incident History - Vodafone Tech Innovation Center Dresden (X = Date, Y = Severity)
Vodafone Tech Innovation Center Dresden cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Vodafone (X = Date, Y = Severity)
Vodafone cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Vodafone Tech Innovation Center Dresden

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