Comparison Overview
資生堂インタラクティブビューティー株式会社

資生堂インタラクティブビューティー株式会社
銀座7-5-5, 中央区, JP
Last Update: 25/02/2026
資生堂グループのIT・DXを牽引する組織、資生堂インタラクティブビューティーです。 変化する環境に対応し、デジタルトランスフォーメーション(DX)を加速させ、資生堂ジャパンの事業モデルを革新していくことを目的に、2021年に誕生。 「資生堂と皆さま」、「リアルとデジタル」、「お客さま同士」といったさまざまな繋がりや関係性を、デジタル・テクノロジー×「ビューティー」の持つ力で革新していきます。

Hitachi
1-6-6, Marunouchi, Chiyoda-ku, Tokyo, Japan, JP, 100-8280
Last Update: 13/09/2026
For over 100 years, Hitachi has been committed to developing innovations that improve lives. Today, this means creating superior technology and products that balance environment, well-being, and economic growth. We integrate IT, operational technology (OT), and produc...
Compliance Ranges Comparison

資生堂インタラクティブビューティー株式会社







Hitachi






Benchmark & Cyber Underwriting Signals
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for 資生堂インタラクティブビューティー株式会社 in 2026.
Incidents vs IT Services and IT Consulting Industry Avg (This Year)
No incidents recorded for Hitachi in 2026.
Incident History - 資生堂インタラクティブビューティー株式会社 (X = Date, Y = Severity)
資生堂インタラクティブビューティー株式会社 cyber incidents detection timeline including parent company and subsidiaries.
Incident History - Hitachi (X = Date, Y = Severity)
Hitachi cyber incidents detection timeline including parent company and subsidiaries.
Notable Incidents

資生堂インタラクティブビューティー株式会社

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