LiveActive security incident?Get immediate response
CVE Record

CVE-2021-40336: HTTP Response Splitting in Hitachi Energy’s MSM Product

A vulnerability exists in the http web interface where the web interface does not validate data in an HTTP header. This causes a possible HTTP response splitting, which if exploited could lead an attacker to channel down harmful code into the user’s web browser, such as to steal the session cookies. Thus, an attacker who successfully makes an MSM user who has already established a session to MSM web interface clicks a forged link to the MSM web interface, e.g., the link is sent per E-Mail, could trick the user into downloading malicious software onto his computer. This issue affects: Hitachi Energy MSM V2.2 and prior versions.

MediumCVSS 5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Hitachi Energy MSM v2.2 and earlier has a web-interface flaw that can let a forged link manipulate HTTP responses. A successful attack requires user interaction and an established MSM session, but could expose session cookies or push harmful browser content.

Executive priority

Treat this as a moderate-priority industrial software issue. It is not reported as actively exploited, but systems with reachable MSM web interfaces should be reviewed promptly because attacks target authenticated users and sessions.

Technical view

The issue is CWE-113 HTTP response splitting caused by insufficient validation of data in an HTTP header. CVSS 3.1 is 5.0 with network attack vector, high complexity, no privileges required, user interaction required, unchanged scope, and low confidentiality, integrity, and availability impact.

Likely exposure

Organizations running Hitachi Energy MSM v2.2 or prior are potentially exposed, especially where the MSM web interface is reachable by users through email-linked browsing paths.

Exploitation context

The provided sources do not indicate active exploitation or KEV listing. Exploitation depends on social engineering: an authenticated MSM user clicks a forged MSM web-interface link while a session is active.

Researcher notes

Evidence is limited to the CVE record and referenced vendor advisory URL. Do not assume exploit availability or a specific patch without checking vendor guidance. Focus validation on affected version, interface reachability, and session-exposure risk.

Mitigation direction

  • Inventory MSM deployments and identify v2.2 or earlier systems.
  • Check Hitachi Energy or ABB advisory guidance for supported remediation.
  • Restrict MSM web-interface access to trusted networks or VPN paths.
  • Warn MSM users against forged links targeting active web sessions.
  • Monitor for suspicious requests and unusual session activity.

Validation and detection

  • Confirm MSM product version and web-interface exposure for each deployment.
  • Verify whether affected systems are reachable from user workstations or broader networks.
  • Review vendor advisory details for fixed versions or compensating controls.
  • Check logs for suspicious header-related requests or forged-link reports.
  • Confirm session handling and cookie protections are configured as documented.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-113: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-40336 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5CVSS 3.1MediumCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L1.63.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5Medium
CVSS 3.1 vector shape for CVE-2021-40336Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Hitachi EnergyMSMv2.2Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-113 · source CWE mapping

Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting')

Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.