Comparison Overview
맥킨지앤드컴퍼니 (McKinsey Korea)

맥킨지앤드컴퍼니 (McKinsey Korea)
54F Three IFC, 10 Gukjegeumyung-ro, Yeongdeungpo-gu, Seoul, Seoul, 07326, KR
Last Update: 31/01/2026
맥킨지앤드컴퍼니(McKinsey & Company)는 세계 유수의 기업, 정부, 공공기관의 신뢰받는 자문 파트너로 활동하는 글로벌 경영 컨설팅 기업입니다. 민간, 공공, 사회 전반에 걸친 다양한 조직들과 협업하며, 깊이 있는 전문성과 폭넓은 글로벌 네트워크를 바탕으로 복잡하고 중요한 과제를 해결합니다. 우리는 고객과 함께 역량과 리더십을 강화하며, 실질적인 해법 도출과 지속 가능한 변화에 기여하는 것을 목표로 합니다. 해당 페이지에서는 맥킨지 한국 오피스의 미디어 활동,...

SJ Group
38 Cleantech Loop, Surbana Jurong Campus, Singapore, SG, 636741
Last Update: 12/09/2026
SJ designs spaces and systems that unlock human potential, delivering connection and certainty on shifting ground. For over 75 years, SJ and its member companies have turned foresight into form and function through urban, infrastructure and managed services consultin...
Compliance Ranges Comparison

맥킨지앤드컴퍼니 (McKinsey Korea)







SJ Group






Benchmark & Cyber Underwriting Signals
Incidents vs Professional Services Industry Avg (This Year)
No incidents recorded for 맥킨지앤드컴퍼니 (McKinsey Korea) in 2026.
Incidents vs Professional Services Industry Avg (This Year)
No incidents recorded for SJ Group in 2026.
Incident History - 맥킨지앤드컴퍼니 (McKinsey Korea) (X = Date, Y = Severity)
맥킨지앤드컴퍼니 (McKinsey Korea) cyber incidents detection timeline including parent company and subsidiaries.
Incident History - SJ Group (X = Date, Y = Severity)
SJ Group cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

맥킨지앤드컴퍼니 (McKinsey Korea)

SJ Group
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.