# CVE-2022-3683: SDM600 API web services authorization validation > An attacker can read sensitive data from an unprotected data store due to insufficient authorization validation in the SDM600 API. - **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 28 Mar 2023 - **Updated:** 18 Feb 2025 - **Also known as:** GHSA-jvf2-gjjh-jg3r ## What is CVE-2022-3683? CVE-2022-3683 is a high-severity missing authorization vulnerability in Hitachi Energy SDM600, published on 28 Mar 2023. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description 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:*:*:*:*:*:*:* Weakness: CWE-285 (Improper Authorization) ## Which versions are affected by CVE-2022-3683? It affects 1 product. Products: Hitachienergy Sdm600. ## How do I fix CVE-2022-3683? No fix has been published for CVE-2022-3683 yet. Limit exposure of the affected software until one is available. ## Is CVE-2022-3683 being exploited? There is no known exploitation of CVE-2022-3683 in the wild and no public exploit code. ## Other vulnerabilities in Hitachi Energy SDM600 - [CVE-2022-3682](https://insights.sbomify.com/CVE-2022-3682/): SDM600 file permission validation (critical 9.9) - [CVE-2022-3684](https://insights.sbomify.com/CVE-2022-3684/): SDM600 endpoint vulnerability (high 7.5) - [CVE-2022-3685](https://insights.sbomify.com/CVE-2022-3685/): SDM600 software privilege level (high 7.5) - [CVE-2022-3686](https://insights.sbomify.com/CVE-2022-3686/): SDM600 API permission check (medium 4.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2022-3683 and fix it if it is affected. What it is: CVE-2022-3683 is a high-severity missing authorization vulnerability in Hitachi Energy SDM600, published on 28 Mar 2023. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2022-3683 in the wild and no public exploit code. Affected product: Hitachi Energy SDM600. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2022-3683/ (Markdown: https://insights.sbomify.com/CVE-2022-3683/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2022-3683 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-3683 - OSV: https://osv.dev/vulnerability/CVE-2022-3683 --- From sbomify Insights: https://insights.sbomify.com/CVE-2022-3683/ Summaries are generated and may contain mistakes; the official description above is the record.