Comparison Overview
Koning & Hartman

Koning & Hartman
Voltastraat 4, Zwijndrecht, Zuid-Holland, 3335 KK, NL
Last Update: 01/04/2026
Technologie speelt een sleutelrol in onze samenleving. Digitalisering leidt tot een hyper-connected wereld waarin technologie leidend is in alle facetten van de samenleving. De oplossingen van Koning & Hartman zijn een combinatie van producten, systemen en diensten, w...

Binance
Everywhere, 0, OO
Last Update: 03/04/2026
Binance is the world’s leading blockchain ecosystem and cryptocurrency infrastructure provider with a product suite that includes the world's largest digital asset exchange and much more. Trusted by over 200 millions of users worldwide, the Binance platform is dedicate...
Compliance Ranges Comparison

Koning & Hartman







Binance






Benchmark & Cyber Underwriting Signals
Incidents vs Technology, Information and Internet Industry Avg (This Year)
No incidents recorded for Koning & Hartman in 2026.
Incidents vs Technology, Information and Internet Industry Avg (This Year)
Binance has 85.19% more incidents than the average of all companies with at least one recorded incident.
Incident History - Koning & Hartman (X = Date, Y = Severity)
Koning & Hartman cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Binance (X = Date, Y = Severity)
Binance cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

Koning & Hartman

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