Comparison Overview
Deutsche Telekom Design & Customer Experience
Deutsche Telekom Design & Customer Experience
Friedrich-Ebert-Allee 140, Bonn, North Rhine-Westphalia, DE, 53113
Last Update: 21/04/2026
The Deutsche Telekom Design & CX Team develops products, services, devices, apps, and interfaces based on customers’ needs and insights. We strive for the best customer experience to ease people’s life and to make technology human centered. To do so, we have built a sa...
A1 Telekom Austria Group
Lassallestrasse 9, Vienna, Vienna, AT, 1020
Last Update: 02/04/2026
WE ARE EMPOWERING DIGITAL LIFE We don't know what the world will look like in 2050, but we know that A1 Telekom Austria Group is geared up for current and future demands. We are a leading provider of digital services and communications solutions in Central and Eastern...
Compliance Ranges Comparison
Deutsche Telekom Design & Customer Experience
A1 Telekom Austria Group
Benchmark & Cyber Underwriting Signals
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for Deutsche Telekom Design & Customer Experience in 2026.
Incidents vs Telecommunications Industry Avg (This Year)
No incidents recorded for A1 Telekom Austria Group in 2026.
Incident History - Deutsche Telekom Design & Customer Experience (X = Date, Y = Severity)
Deutsche Telekom Design & Customer Experience cyber incidents detection timeline including parent company and subsidiaries.
Incident History - A1 Telekom Austria Group (X = Date, Y = Severity)
A1 Telekom Austria Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
Deutsche Telekom Design & Customer Experience
A1 Telekom Austria Group
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.