Sdm600Application · Hitachienergy

CVE-2022-3682

HIGH · 8.8 CVSS v3.1 Published 2023-03-28

Fix available

A fix is available. Upgrade to 1.3.0.1339 or later.

See remediation →

94/100

Remediation priority · Urgent

Remotely reachable Zero-click

Official description

NVD · unedited

A vulnerability exists in the SDM600 file permission validation. An attacker could exploit the vulnerability by gaining access to the system and uploading a specially crafted message to the system node, which could result in Arbitrary code Executing. 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

dbcve analysis · moderate confidence

A file permission validation vulnerability exists in Hitachi Energy SDM600. An authenticated attacker with system access can upload a specially crafted message to a system node, bypassing file permission checks and achieving arbitrary code execution. This affects all versions prior to 1.2 FP3 HF4 (Build 1.2.23000.291).

MitigationUpgrade SDM600 to version 1.2 FP3 HF4 (Build Nr. 1.2.23000.291) or later. Until patched, limit system access to trusted personnel and implement network segmentation to reduce attack surface.

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

Affected products & versions

NVD · CPE data

Sdm600Application

Affected:>= 1.0, < 1.3.0.1339

CVSS breakdown

From the vector

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

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

Am I affected?

dbcve checks

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

Identify SDM600 software version

Locate the installed version of SDM600 through the product's system information page, about dialog, or version check command provided in the product documentation

Affected if The installed version falls within >= 1.0 and < 1.3.0.1339 (or is earlier than Build 1.2.23000.291)
Confirm file upload capability is enabled

Inspect the SDM600 configuration settings or system features to determine whether the message upload functionality to system nodes is accessible

Affected if File/message upload to system nodes is permitted and accessible to the user account in question
Verify authentication controls

Review access control settings and user privilege configurations to determine if low-privilege or external authenticated users can access the system

Affected if Authenticated users with limited privileges can reach the system upload functionality
Check network exposure

Examine network configuration to determine if SDM600 management interface is accessible from untrusted networks

Affected if The system is reachable from networks outside the trusted administrative zone

The environment is affected if SDM600 version is below 1.3.0.1339 (or Build 1.2.23000.291) and the file upload feature to system nodes is accessible to authenticated users.

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

Remediation

dbcve · scoped

Upgrade available Upgrade to 1.3.0.1339 or later

Fixed in 1.3.0.1339

Interim mitigation

Upgrade SDM600 to version 1.2 FP3 HF4 (Build Nr. 1.2.23000.291) or later. Until patched, limit system access to trusted personnel and implement network segmentation to reduce attack surface.

Recommended fix Moderate confidence

1.2 FP3 HF4 (Build Nr. 1.2.23000.291) or later

Obtain the fixed version of SDM600 (version 1.2 FP3 HF4 with Build Nr. 1.2.23000.291 or later) from the official Hitachi Energy support portal at search.abb.com
Review the SDM600 upgrade documentation and release notes for version 1.2 FP3 HF4
Ensure proper backup of the current SDM600 configuration and data
Schedule a maintenance window as upgrades may require system downtime
Apply the upgrade following Hitachi Energy's documented installation procedure for SDM600 firmware
After upgrade, verify that the file permission validation vulnerability has been addressed by confirming the version number in the system

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

Fix this in Sdm600 Scoped from the published advisory

Consultation4.0 h
Implementation16.0 h
Testing8.0 h
Review / QA4.0 h

32.0 hours of engineering $5,600

Get the upgrade done

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

search.abb.comVendor Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2022-3682?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsUpgrade to 1.3.0.1339 or later

Severity 8.8 High

Exploit likelihood EPSS, next 30 days 0.8%

Affects: Sdm600

Remediation

A high-priority fix

Fix this in Sdm600 32 hrs · Moderate

Typical engagement from $5,600

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2022-3682 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References