Sdm600Application · Hitachienergy

CVE-2022-3683

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

NVD · unedited

A vulnerability exists in the SDM600 API web services authorization validation implementation. An attacker who successfully exploits the vulnerability could read data directly from a data store that is not restricted, or insufficiently protected, having access to sensitive data. 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 · high confidence

Broken access control vulnerability in Hitachi Energy SDM600 API web services where authorization validation is insufficiently implemented, allowing unauthenticated or unauthorized attackers to read sensitive data directly from unprotected data stores via the API.

MitigationUpgrade SDM600 to version 1.2 FP3 HF4 (Build Nr. 1.2.23000.291) or later to remediate the authorization validation flaw. Until patched, restrict network access to API endpoints and monitor for unauthorized data access attempts.

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

CVSS breakdown

From the vector

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

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

Am I affected?

dbcve checks

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

Identify SDM600 software version

Locate the SDM600 installation directory and check the version information file, typically found in the product's About or System Information section of the management interface, or by running 'sdm600 --version' if the command-line tool is available

Affected if Version is 1.0 through 1.2.23000.290 (any version less than 1.2.23000.291)
Verify API web services are enabled

Access the SDM600 administration interface and navigate to the API configuration or web services settings to confirm whether the API is currently enabled

Affected if API web services are enabled and running
Check API endpoint exposure

Attempt to access the API endpoints directly using a web browser or HTTP client (such as curl) without providing credentials - typical API paths include /api/data, /api/datastore, or /sdm600/api/ endpoints

Affected if API endpoints respond to unauthenticated requests or return data without requiring authorization tokens
Review API access control configuration

Examine the SDM600 security or access control settings within the administration panel to verify whether API authorization validation is properly configured

Affected if Authorization validation is disabled, set to permissive levels, or missing for sensitive data endpoints

The environment is affected if SDM600 version is 1.0 or higher but below 1.2.23000.291 AND the API web services are exposed or accessible on the network.

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

Remediation

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 to remediate the authorization validation flaw. Until patched, restrict network access to API endpoints and monitor for unauthorized data access attempts.

Recommended fix High confidence

1.2 FP3 HF4 (Build Nr. 1.2.23000.291)

Identify the current installed version of SDM600 by checking the system documentation or web interface
Contact ABB/Hitachi Energy technical support or visit the official support portal (search.abb.com) to obtain the upgrade package
Request version 1.2 FP3 HF4 (Build Nr. 1.2.23000.291) or later
Follow the vendor's official upgrade procedure documentation to apply the update
Verify the upgrade was successful by checking the version information after installation
Test the API web services to confirm proper authorization controls are functioning

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

Fix this in Sdm600 Scoped from the published advisory

Consultation3.0 h
Implementation4.0 h
Testing6.0 h
Review / QA3.0 h

16.0 hours of engineering $2,760

Get the upgrade done

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2022-3683 — 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-3683 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2022-3683?

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.2.23000.291 or later

Severity 7.5 High

Exploit likelihood EPSS, next 30 days 0.5%

Affects: Sdm600

Remediation

A high-priority fix

Fix this in Sdm600 16 hrs · Moderate

Typical engagement from $2,760

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2022-3683 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