Comparison Overview
CJ Logistics

CJ Logistics
7, Jong-ro 5-gil, Jongno-gu, Seoul, Seoul, -, KR, 03157
Last Update: 18/01/2026
[About] "WE DESIGN LOGISTICS" CJ Logistics will become a global leader of logistics based on constant innovation and challenge. [Company Overview] CJ Logistics leads the way in supply chain technology, engineering, systems and solutions as well as SCM consulting. Eve...

A.P. Moller - Maersk
Esplanaden 50, Copenhagen, DK, 1098
Last Update: 14/09/2026
A.P. Moller - Maersk is an integrated transport and logistics company; going all the way, together, for our customers and society. ALL THE WAY is our commitment to connect the world so that everyone has both the possibility and the ability to trade, grow and thrive. The...
Compliance Ranges Comparison

CJ Logistics







A.P. Moller - Maersk






Benchmark & Cyber Underwriting Signals
Incidents vs Transportation, Logistics, Supply Chain and Storage Industry Avg (This Year)
No incidents recorded for CJ Logistics in 2026.
Incidents vs Transportation, Logistics, Supply Chain and Storage Industry Avg (This Year)
No incidents recorded for A.P. Moller - Maersk in 2026.
Incident History - CJ Logistics (X = Date, Y = Severity)
CJ Logistics cyber incidents detection timeline including parent company and subsidiaries.
Incident History - A.P. Moller - Maersk (X = Date, Y = Severity)
A.P. Moller - Maersk cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

CJ Logistics

A.P. Moller - Maersk
FAQ
Latest Global CVEs
Heym from 0.0.55 before 0.0.121 contains a privilege escalation vulnerability that allows shared collaborators to overwrite a workflow's error_workflow_id because the field is missing from OWNER_ONLY_EXECUTION_FIELDS. Attackers can point the error workflow to their own workflow with an HTTP node, and when the parent workflow errors the owner's decrypted credentials are injected and exfiltrated.
Nodemailer from 3.0.0 before 10.0.10 contains a quadratic complexity denial of service vulnerability in the SMTP client reply parser in SMTPConnection._onData and isPartialResponse. A malicious SMTP server or on-path attacker can stream continuation lines without a completion line before authentication, blocking the Node.js event loop and exhausting memory.
Nodemailer from 3.0.0 before 10.0.10 contains a denial of service vulnerability in MessageParser.parseHeaders that allows users to exhaust CPU through quadratic header unfolding. Attackers can supply large recipient lists or long headers that fold into tens of thousands of continuation lines, blocking the Node.js event loop during DKIM signing.
Nodemailer from 3.0.0 before 10.0.13 contains an improper input validation vulnerability in its address parser that fails to strip RFC 5322 comments inside angle-bracket addresses. Attackers can supply recipients like a display name with a parenthesized comment in the domain, so illegal characters reach envelope.to and RCPT TO, causing rejected delivery or parser interpretation conflicts that bypass domain allow-lists.
Nodemailer 3.0.0 before 10.0.13 has a regular expression denial of service in SMTPConnection._actionEHLO, whose four AUTH mechanism detection regexes contain overlapping whitespace sub-patterns that backtrack quadratically. A malicious or man-in-the-middle SMTP server can reply to EHLO with 250-AUTH, a long whitespace run and a non-matching token, blocking the Node.js event loop for tens of seconds to hours before authentication.