Comparison Overview
McKinsey & Company Japan

McKinsey & Company Japan
六本木1-9-10 アークヒルズ仙石山森タワー, 港区, 106-0032, JP
Last Update: 28/12/2025
マッキンゼー・アンド・カンパニージャパンは1971年の設立以来、日本企業の成長に貢献してまいりました。2018年には関西オフィスを開設し、西日本においても企業の持続的な発展を目指して活動しております。 戦略再構築・事業収益変革・組織人材変革・デジタル化・グローバル化・ESG等の喫緊の経営課題解決をトップマネジメントと協業。企業・組織の飛躍的変革と持続的発展に尽力いたします。

Boston Consulting Group (BCG)
200 Pier 4 Blvd, Boston, Massachusetts, US, 02210
Last Update: 19/06/2026
Boston Consulting Group partners with leaders in business and society to tackle their most important challenges and capture their greatest opportunities. BCG was the pioneer in business strategy when it was founded in 1963. Today, we work closely with clients to embrace...
Compliance Ranges Comparison

McKinsey & Company Japan







Boston Consulting Group (BCG)






Benchmark & Cyber Underwriting Signals
Incidents vs Business Consulting and Services Industry Avg (This Year)
No incidents recorded for McKinsey & Company Japan in 2026.
Incidents vs Business Consulting and Services Industry Avg (This Year)
Boston Consulting Group (BCG) has 4.76% fewer incidents than the average of all companies with at least one recorded incident.
Incident History - McKinsey & Company Japan (X = Date, Y = Severity)
McKinsey & Company Japan cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Boston Consulting Group (BCG) (X = Date, Y = Severity)
Boston Consulting Group (BCG) cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

McKinsey & Company Japan

Boston Consulting Group (BCG)
FAQ
Latest Global CVEs
Deserialization of untrusted data in Microsoft Edge (Chromium-based) allows an unauthorized attacker to execute code over a network.
The Bluetooth BAP Broadcast Assistant GATT client in subsys/bluetooth/audio/bap_broadcast_assistant.c reassembled remote Broadcast Receive State data into a single file-static net_buf_simple (att_buf, BT_ATT_MAX_ATTRIBUTE_LEN = 512 bytes) shared by all connection instances, while the BUSY flag, long-read handle, and reset/offset state were per-connection. When the device acts as a Broadcast Assistant connected to multiple Scan Delegator peripherals, notification and long-read callbacks from different connections interleave on the shared buffer: the append in notify_handler (net_buf_simple_add_mem at the not-busy branch) performs no tailroom check, so receive-state notifications from two or more delegators accumulate on the same 512-byte buffer and, with a sufficiently large configured ATT MTU (BT_L2CAP_TX_MTU up to 2000) and two-to-three concurrent connections, write past the buffer into adjacent .bss (net_buf_simple_add only asserts in debug builds). Even below the overflow threshold, one connection's net_buf_simple_reset zeroes the shared length while another connection's reassembly and GATT read offset are in flight, mixing one peer's data into another's parse. A malicious or compromised Scan Delegator (or two colluding peers) over BLE can trigger this, causing out-of-bounds writes (memory corruption / denial of service) and cross-connection data corruption. The fix moves the buffer into the per-connection instance struct so each connection reassembles into its own buffer. Affects Zephyr releases shipping the Broadcast Assistant with the shared buffer, including v4.4.0 and earlier.
ImageMagick before 7.1.2-26 contains a memory leak vulnerability in the VIFF encoder when memory allocation fails. Attackers can trigger allocation failures by processing specially crafted VIFF images to exhaust available memory and cause denial of service.
ImageMagick before 7.1.2-26 contains a use-after-free vulnerability in the FormatMagickCaption method when memory allocation fails. Attackers can trigger memory allocation failures to cause a dangling pointer to reference freed memory, potentially enabling denial of service or code execution.
ImageMagick before 7.1.2-26 contains a policy bypass vulnerability in the APNG encoder and external delegates due to missing validation checks. Attackers can write files to disallowed paths by bypassing configured policy restrictions through the APNG encoding process.