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)는 세계 유수의 기업, 정부, 공공기관의 신뢰받는 자문 파트너로 활동하는 글로벌 경영 컨설팅 기업입니다. 민간, 공공, 사회 전반에 걸친 다양한 조직들과 협업하며, 깊이 있는 전문성과 폭넓은 글로벌 네트워크를 바탕으로 복잡하고 중요한 과제를 해결합니다. 우리는 고객과 함께 역량과 리더십을 강화하며, 실질적인 해법 도출과 지속 가능한 변화에 기여하는 것을 목표로 합니다. 해당 페이지에서는 맥킨지 한국 오피스의 미디어 활동,...
Hatch
2800 Speakman Dr, Mississauga, Ontario, CA, L5K2R7
Last Update: 30/03/2026
Our organization is passionately committed to the pursuit of a better world through positive change. We embrace your visions as our own and partner with you to develop better ideas that are smarter, more efficient, and innovative. Our global network of 10,000 profession...
Compliance Ranges Comparison
맥킨지앤드컴퍼니 (McKinsey Korea)
Hatch
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 Hatch in 2026.
Incident History - 맥킨지앤드컴퍼니 (McKinsey Korea) (X = Date, Y = Severity)
맥킨지앤드컴퍼니 (McKinsey Korea) cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Hatch (X = Date, Y = Severity)
Hatch cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents
맥킨지앤드컴퍼니 (McKinsey Korea)
Hatch
FAQ
Latest Global CVEs
A security vulnerability has been detected in adafap api-mcp up to 92b9a5d04acfec165c7d4ef852496593aa87be06. This affects the function customAxios of the file app/api/proxy/route.ts of the component Proxy API Endpoint. The manipulation of the argument url leads to server-side request forgery. The attack is possible to be carried out remotely. This product adopts a rolling release strategy to maintain continuous delivery. Therefore, version details for affected or updated releases cannot be specified. The project was informed of the problem early through an issue report but has not responded yet.
A weakness has been identified in PhialsBasement KoboldCPP-MCP-Server 1.0.0. Affected by this issue is the function makeRequest of the file src/index.ts of the component BaseConfigSchema. Executing a manipulation of the argument apiUrl can lead to server-side request forgery. It is possible to launch the attack on the local host. The project was informed of the problem early through an issue report but has not responded yet.
A security flaw has been discovered in Handwriting-OCR handwriting-ocr-mcp-server 0.1.0. Affected by this vulnerability is the function fs.readFileSync of the file src/index.ts of the component upload_document. Performing a manipulation of the argument File results in path traversal. Attacking locally is a requirement. The project was informed of the problem early through an issue report but has not responded yet.
A vulnerability was identified in Nikolaibibo claude-comfyui-mcp 1.0.0. Affected is the function copyFileSync of the file src/tools/utils.ts of the component comfy_upload_image. Such manipulation of the argument image_path leads to path traversal. An attack has to be approached locally. The project was informed of the problem early through an issue report but has not responded yet.
A Server-Side Request Forgery (SSRF) vulnerability exists in nltk/nltk versions 3.9.4 and the current develop branch. The `nltk.pathsec.validate_network_url()` function, intended to prevent SSRF by rejecting internal network addresses, fails to reject IPs in the RFC 6598 shared address space (`100.64.0.0/10`). This occurs because Python's `ipaddress` module does not classify such addresses as `is_private` or `is_global`, and the current guard only checks `is_private` and a few explicit categories. An attacker who can influence a URL passed to NLTK's network-loading helpers can exploit this vulnerability to make a strict-mode application send requests to shared-address-space hosts, potentially exposing non-public infrastructure reachable from the application host. The impact is limited to SSRF-style confidentiality exposure, with no code execution claimed.