dbcve.org
Opc Server For Ac 800mApplication · Abb

CVE-2021-22284

HIGH · 8.8 CVSS v3.1 Published 2022-02-04
Fix available
A fix is available. Upgrade to 6.0.0-4 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
Incorrect Permission Assignment for Critical Resource vulnerability in OPC Server for AC 800M allows an attacker to execute arbitrary code in the node running the AC800M OPC Server.

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 · moderate confidence

An incorrect permission assignment vulnerability in the OPC Server for AC 800M allows unauthorized users or processes to modify critical system resources such as executable files, configuration files, or DLLs. This permission misconfiguration enables an attacker to inject or replace code that the OPC Server will execute, leading to arbitrary code execution on the node.

MitigationRestrict file system permissions on the OPC Server for AC 800M installation directory, binaries, and configuration files to only authorized administrators/service accounts, removing any world-writable or group-writable permissions that allow unauthorized code injection or modification.

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
Opc Server For Ac 800mApplication
Affected:>= 5.1.0-0, < 6.0.0-4

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
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? 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. Verify OPC Server for AC 800M is installed
    Check for the product in Windows Programs and Features, or search for installation directories like C:\Program Files\ABB\OPC Server for AC 800M or C:\ABB\OPC Server for AC 800M
    Affected if Product is installed with version >= 5.1.0-0 and < 6.0.0-4
  2. Check installed version number
    Right-click on the installed ABB OPC Server for AC 800M entry in Programs and Features and select Properties, or check the version info of the main executable (e.g., Ac800MConnect.exe or OPCServerAC800M.exe) in the installation folder
    Affected if Version displayed is between 5.1.0-0 and 6.0.0-4 (exclusive)
  3. Inspect installation directory permissions
    Right-click the installation folder, select Properties, go to the Security tab, and review the permissions for Users, Everyone, and other groups
    Affected if Users group or Everyone has Write or Modify permissions on the installation directory
  4. Check executable file permissions
    Right-click each executable file in the installation folder (e.g., .exe and .dll files), open Properties, Security tab, and verify write permissions are not granted to unauthorized accounts
    Affected if Any user account or group other than Administrators has Write permission on executable or DLL files
  5. Review configuration file permissions
    Examine permissions on configuration files (e.g., .ini, .xml, .cfg files) in the installation directory - right-click each, check Security tab
    Affected if Configuration files are writable by Users, Everyone, or other non-admin groups

If the product version is 5.1.0-0 through 6.0.0-3 AND the installation directory, executables, or config files have Write/Modify permissions granted to non-administrator users or groups, 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 6.0.0-4 or later
Fixed in 6.0.0-4
Interim mitigation

Restrict file system permissions on the OPC Server for AC 800M installation directory, binaries, and configuration files to only authorized administrators/service accounts, removing any world-writable or group-writable permissions that allow unauthorized code injection or modification.

Recommended fix Moderate confidence

Upgrade to OPC Server for AC 800M version 6.0.0-4 or later

  1. Confirm the current installed version of OPC Server for AC 800M
  2. Review the 800M Engineer's documentation for upgrade procedures and prerequisites
  3. Create a full backup of the current configuration and project files
  4. Stop all OPC Server services and related processes
  5. Upgrade OPC Server for AC 800M to version 6.0.0-4 or later
  6. Verify the installation was successful and services start correctly
  7. Validate that existing projects and configurations load properly
  8. Confirm the vulnerability is remediated
Caveat Refer to release notes for version 6.0.0 for any functional changes or migration requirements from prior versions

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

Fix this in Opc Server For Ac 800m Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
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,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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