Comparison Overview
S-Communication Services GmbH

S-Communication Services GmbH
Friedrichstraße 50, Berlin, 10117, DE
Last Update: 02/04/2026
S-Com ist Transformationstreiber und zentraler Dienstleister der Sparkassen-Finanzgruppe. Gemeinsam arbeiten wir an der laufenden Verbesserung etablierter Standards und setzen dort neue, wo wir Markenerlebnis und Kundenreise weiter optimieren können. Wir begleiten Insti...

NetEase
No.599 Wangshang Road, Binjiang District, Hangzhou, 310052, CN
Last Update: 31/03/2026
As a leading internet technology company based in China, NetEase, Inc. (NASDAQ: NTES and HKEX:9999, "NetEase") provides premium online services centered around content creation. With extensive offerings across its expanding gaming ecosystem, NetEase develops and operat...
Compliance Ranges Comparison

S-Communication Services GmbH







NetEase






Benchmark & Cyber Underwriting Signals
Incidents vs Technology, Information and Internet Industry Avg (This Year)
No incidents recorded for S-Communication Services GmbH in 2026.
Incidents vs Technology, Information and Internet Industry Avg (This Year)
No incidents recorded for NetEase in 2026.
Incident History - S-Communication Services GmbH (X = Date, Y = Severity)
S-Communication Services GmbH cyber incidents detection timeline including parent company and subsidiaries.
Incident History - NetEase (X = Date, Y = Severity)
NetEase cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

S-Communication Services GmbH

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