dbcve.org
Sdm600Application · Hitachienergy

CVE-2022-3684

HIGH · 7.5 CVSS v3.1 Published 2023-03-28
Fix available
A fix is available. Upgrade to 1.2.23000.291 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability exists in a SDM600 endpoint. An attacker could exploit this vulnerability by running multiple parallel requests, the SDM600 web services become busy rendering the application unresponsive. This issue affects: All SDM600 versions prior to version 1.2 FP3 HF4 (Build Nr. 1.2.23000.291) List of CPEs: * cpe:2.3:a:hitachienergy:sdm600:1.0:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:sdm600:1.1:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:sdm600:1.2:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:sdm600:1.2.9002.257:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:sdm600:1.2.10002.257:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:sdm600:1.2.11002.149:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:sdm600:1.2.12002.222:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:sdm600:1.2.13002.72:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:sdm600:1.2.14002.44:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:sdm600:1.2.14002.92:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:sdm600:1.2.14002.108:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:sdm600:1.2.14002.182:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:sdm600:1.2.14002.257:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:sdm600:1.2.14002.342:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:sdm600:1.2.14002.447:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:sdm600:1.2.14002.481:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:sdm600:1.2.14002.506:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:sdm600:1.2.14002.566:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:sdm600:1.2.20000.3174:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:sdm600:1.2.21000.291:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:sdm600:1.2.21000.931:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:sdm600:1.2.21000.105:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:sdm600:1.2.23000.291:*:*:*:*:*:*:*

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a denial of service (DoS) vulnerability in Hitachi Energy SDM600 web services. An attacker can exploit the endpoint by sending multiple parallel requests, causing the web services to become overwhelmed and unresponsive. The vulnerability stems from insufficient handling of concurrent requests at the application layer, allowing resource exhaustion through parallel request attacks.

MitigationUpgrade to SDM600 version 1.2 FP3 HF4 (Build Nr. 1.2.23000.291) or later. As an interim measure, implement rate limiting on the web services endpoint and restrict network access to the service.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Sdm600Application
Affected:>= 1.0, < 1.2.23000.291

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify SDM600 software version
    Locate the installed version of Hitachi Energy SDM600 in the system information, about page, or product documentation. This is typically visible in the web interface login page, system settings, or installed programs list.
    Affected if The installed version is 1.0 or higher but lower than 1.2.23000.291
  2. Confirm web services are enabled
    Access the SDM600 web interface and verify that web services (REST API, SOAP endpoints, or similar) are enabled in the configuration settings.
    Affected if Web services are enabled and accessible on the network
  3. Check network exposure
    Review firewall rules, network ACLs, or access control lists to determine if the SDM600 web services endpoint is reachable from network segments outside the trusted zone.
    Affected if The web services are exposed to untrusted networks or the internet
  4. Verify concurrent request handling
    If you have access to logs or monitoring tools, check for any existing evidence of service degradation, timeouts, or failures under normal load conditions.
    Affected if The system shows signs of instability or unavailability under concurrent request loads
  5. Review current rate limiting configuration
    Inspect the web services configuration for any rate limiting, throttling, or request queuing settings that may be currently applied.
    Affected if No rate limiting or throttling mechanisms are configured for the web services endpoint

A user is affected if SDM600 version is 1.0 through 1.2.23000.290 (inclusive) AND web services are enabled and accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.2.23000.291 or later
Fixed in 1.2.23000.291
Interim mitigation

Upgrade to SDM600 version 1.2 FP3 HF4 (Build Nr. 1.2.23000.291) or later. As an interim measure, implement rate limiting on the web services endpoint and restrict network access to the service.

Recommended fix High confidence

1.2 FP3 HF4 (Build Nr. 1.2.23000.291) or later

  1. 1. Identify the current installed version of SDM600 by accessing the device or checking system documentation.
  2. 2. Verify if the current version is below Build Nr. 1.2.23000.291 (versions prior to 1.2 FP3 HF4).
  3. 3. Contact ABB/Hitachi Energy technical support to obtain the upgrade package for version 1.2 FP3 HF4 (Build Nr. 1.2.23000.291) or later.
  4. 4. Follow the vendor's official upgrade procedure to apply the firmware/software update.
  5. 5. After upgrade, verify the new version is 1.2.23000.291 or higher and confirm the web services are functioning normally.
Caveat Review vendor release notes for any compatibility or configuration changes in version 1.2 FP3 HF4 before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Sdm600 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-3684 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-3684 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data