dbcve.org
Sdm600Application · Hitachienergy

CVE-2022-3686

CRITICAL · 9.1 CVSS v3.1 Published 2023-03-28
Fix available
A fix is available. Upgrade to 1.2.23000.291 or later.
See remediation →
100/100
Remediation priority · Urgent
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 · high confidence

This is a denial-of-service vulnerability in Hitachi Energy SDM600 web services. An attacker can exhaust available resources by sending multiple parallel requests, causing the web services to become busy and rendering the application unresponsive. The vulnerability affects all versions prior to 1.2 FP3 HF4 (Build Nr. 1.2.23000.291).

MitigationUpgrade SDM600 to version 1.2 FP3 HF4 (Build Nr. 1.2.23000.291) or later. As a temporary compensating control, implement rate limiting or request throttling at the network perimeter to restrict the number of concurrent requests.

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
High
Integrity
High
Availability
None

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

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. Locate the installed SDM600 version
    Access the SDM600 product interface, typically through the administrative console or about page, and record the exact version number and build number displayed
    Affected if The displayed version is 1.0 or higher but lower than 1.2.23000.291 (Build Nr. 1.2.23000.291)
  2. Verify the exact build number
    Confirm the build number (Build Nr.) in the version details. This is the definitive identifier for determining if the version is vulnerable
    Affected if The build number is less than 1.2.23000.291
  3. Confirm web services are exposed
    Determine if the SDM600 web services interface is accessible from the network. Check network configuration, firewall rules, or service binding settings to see if web services are enabled and reachable
    Affected if Web services are enabled and accessible from network segments accessible to potential attackers
  4. Check for parallel request handling
    Review the web services configuration to understand how concurrent requests are handled. Look for any existing rate limiting or throttling configurations that may be present
    Affected if No rate limiting or request throttling is configured and the version falls within the affected range

If the installed SDM600 version is 1.0 or higher but below build 1.2.23000.291 and the web services interface is network-accessible, the environment is affected by this vulnerability.

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 SDM600 to version 1.2 FP3 HF4 (Build Nr. 1.2.23000.291) or later. As a temporary compensating control, implement rate limiting or request throttling at the network perimeter to restrict the number of concurrent requests.

Recommended fix High confidence

1.2 FP3 HF4 (Build Nr. 1.2.23000.291)

  1. Identify the current installed version of SDM600 by accessing the web interface or checking system information
  2. Download the fixed version 1.2 FP3 HF4 (Build Nr. 1.2.23000.291) from the official ABB (Hitachi Energy) support portal at search.abb.com
  3. Follow the standard SDM600 firmware upgrade procedure: back up the current configuration, upload the new firmware version, verify the installation, and restart the service if required
  4. After upgrade, verify that the web services are responsive and that the vulnerability is mitigated by testing with multiple parallel requests

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

Fix this in Sdm600 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,320
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-3686 — 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-3686 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