Comparison Overview
ICE Digital Trade (formerly essDOCS)

ICE Digital Trade (formerly essDOCS)
N/A
Last Update: 22/01/2026
ICE Digital Trade (IDT), formerly known as essDOCS, provides paperless global trade management solutions which digitize, automate, and accelerate trade & post-trade operations, finance, logistics, compliance, and visibility. 70,000+ companies – including leading commod...

DHL
Charles-de-Gaulle-Str. 20, Bonn, DE, 53113
Last Update: 28/04/2026
DHL is the leading global brand in the logistics industry. Our divisions offer an unrivaled portfolio of logistics services ranging from national and international parcel delivery, e-commerce shipping and fulfillment solutions, international express, road, air and ocean...
Compliance Ranges Comparison

ICE Digital Trade (formerly essDOCS)







DHL






Benchmark & Cyber Underwriting Signals
Incidents vs Transportation, Logistics, Supply Chain and Storage Industry Avg (This Year)
No incidents recorded for ICE Digital Trade (formerly essDOCS) in 2026.
Incidents vs Transportation, Logistics, Supply Chain and Storage Industry Avg (This Year)
DHL has 7.41% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - ICE Digital Trade (formerly essDOCS) (X = Date, Y = Severity)
ICE Digital Trade (formerly essDOCS) cyber incidents detection timeline including parent company and subsidiaries.
Incident History - DHL (X = Date, Y = Severity)
DHL cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

ICE Digital Trade (formerly essDOCS)

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