# CVE-2021-22283: MMS File Transfer Vulnerability impact on Distribution Automation products > Improper initialization in ABB Relion protection relays allows communication channel manipulation, impacting distribution automation security. - **Severity:** Medium 6.2 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 28 Feb 2023 - **Updated:** 7 Mar 2025 - **Also known as:** GHSA-wxvf-mm56-j2pq ## What is CVE-2021-22283? CVE-2021-22283 is a medium-severity vulnerability in ABB Merging Unit- SMU615, published on 28 Feb 2023. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description Improper Initialization vulnerability in ABB Relion protection relays - 611 series, ABB Relion protection relays - 615 series IEC 4.0 FP1, ABB Relion protection relays - 615 series CN 4.0 FP1, ABB Relion protection relays - 615 series IEC 5.0, ABB Relion protection relays - 615 series IEC 5.0 FP1, ABB Relion protection relays - 620 series IEC/CN 2.0, ABB Relion protection relays - 620 series IEC/CN 2.0 FP1, ABB Relion protection relays - REX640 PCL1, ABB Relion protection relays - REX640 PCL2, ABB Relion protection relays - REX640 PCL3, ABB Relion protection relays - RER615, ABB Remote Monitoring and Control - REC615, ABB Merging Unit- SMU615 allows Communication Channel Manipulation.This issue affects Relion protection relays - 611 series: from 1.0.0 before 2.0.3; Relion protection relays - 615 series IEC 4.0 FP1: from 4.1.0 before 4.1.9; Relion protection relays - 615 series CN 4.0 FP1: from 4.1.0 before 4.1.8; Relion protection relays - 615 series IEC 5.0: from 5.0.0 before 5.0.12; Relion protection relays - 615 series IEC 5.0 FP1: from 5.1.0 before 5.1.20; Relion protection relays - 620 series IEC/CN 2.0: from 2.0.0 before 2.0.11; Relion protection relays - 620 series IEC/CN 2.0 FP1: from 2.1.0 before 2.1.15; Relion protection relays - REX640 PCL1: from 1.0.0 before 1.0.8; Relion protection relays - REX640 PCL2: from 1.1.0 before 1.1.4; Relion protection relays - REX640 PCL3: from 1.2.0 before 1.2.1; Relion protection relays - RER615: from 2.0.0 before 2.0.3; Remote Monitoring and Control - REC615: from 1.0.0 before 2.0.3; Merging Unit- SMU615: from 1.0.0 before 1.0.2. Weakness: CWE-665 (Improper Initialization) ## Which versions are affected by CVE-2021-22283? It affects 19 products. Products: Abb Evd4 Firmware, Abb Rec615 Firmware, Abb Red615 Iec Firmware, Abb Ref615 Ansi Firmware, Abb Ref615 Iec Firmware, Abb Ref615r Firmware, Abb Relion 611 Firmware, Abb Relion 615 Ansi Firmware, Abb Relion 615 Cn Firmware, Abb Relion 615 Iec Firmware, Abb Relion 620 Ansi Firmware, Abb Relion 620 Cn Firmware, Abb Relion 620 Iec Firmware, Abb Rer615 Firmware, Abb Rer620 Firmware, Abb Rex640 Pcl1 Firmware, Abb Rex640 Pcl2 Firmware, Abb Rex640 Pcl3 Firmware, Abb Smu615 Firmware. ## How do I fix CVE-2021-22283? No fix has been published for CVE-2021-22283 yet. Limit exposure of the affected software until one is available. ## Is CVE-2021-22283 being exploited? There is no known exploitation of CVE-2021-22283 in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2021-22283 and fix it if it is affected. What it is: CVE-2021-22283 is a medium-severity vulnerability in ABB Merging Unit- SMU615, published on 28 Feb 2023. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2021-22283 in the wild and no public exploit code. Affected product: ABB Merging Unit- SMU615. 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-2021-22283/ (Markdown: https://insights.sbomify.com/CVE-2021-22283/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2021-22283 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2021-22283 - OSV: https://osv.dev/vulnerability/CVE-2021-22283 --- From sbomify Insights: https://insights.sbomify.com/CVE-2021-22283/ Summaries are generated and may contain mistakes; the official description above is the record.