dbcve.org
Automation BuilderApplication · Abb

CVE-2022-31216

HIGH · 7.8 CVSS v3.1 Published 2022-06-15
Fix available
A fix is available. Upgrade to 2.7.1 or later.
See remediation →
80/100
Remediation priority · High
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
Vulnerabilities in the Drive Composer allow a low privileged attacker to create and write to a file anywhere on the file system as SYSTEM with arbitrary content as long as the file does not already exist. The Drive Composer installer file allows a low-privileged user to run a "repair" operation on the product.

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

Drive Composer contains a local privilege escalation vulnerability where the installer repair functionality allows a low-privileged user to create and write files anywhere on the filesystem with SYSTEM privileges, limited only to new files that do not already exist.

MitigationRestrict or disable the repair operation for low-privileged users and apply vendor patches when available to prevent unauthorized SYSTEM-level file writes.

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
Automation BuilderApplication
Affected:>= 1.1.0, <= 2.5.0
Drive ComposerApplication
Affected:>= 2.0, < 2.7.1
Mint WorkbenchApplication
Affected:<= 5866

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/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. Identify installed ABB software
    Check Program Files for ABB directories, or look for ABB Automation Builder, Drive Composer, or Mint Workbench in Add/Remove Programs
    Affected if Any of the affected products (Automation Builder, Drive Composer, or Mint Workbench) are installed
  2. Determine installed version
    Check the version of the installed ABB product in the registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall or in the application's About/Help section
    Affected if Version falls within affected ranges: Automation Builder 1.1.0-2.5.0, Drive Composer 2.0 to <2.7.1, or Mint Workbench <=5866
  3. Verify repair functionality exists
    Locate the installer repair executable within the ABB installation directory, typically found in a bin or installer subfolder
    Affected if The repair executable exists in the installation directory
  4. Check repair feature permissions
    Use icacls or AccessEnum to examine which user groups can execute the repair functionality and write to installation directories
    Affected if Low-privileged users (non-admin) have execute permission on the repair feature or can trigger it through the application interface
  5. Verify SYSTEM-level execution context
    Attempt to monitor or trace the repair process execution context using process monitoring tools to confirm it runs with elevated SYSTEM privileges
    Affected if The repair process executes under the SYSTEM account rather than the invoking user's context

The environment is affected if any ABB Automation Builder (1.1.0-2.5.0), Drive Composer (2.0 to <2.7.1), or Mint Workbench (<=5866) is installed AND low-privileged users can access the repair functionality which runs with SYSTEM privileges.

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 2.7.1 or later
Fixed in 2.7.1
Interim mitigation

Restrict or disable the repair operation for low-privileged users and apply vendor patches when available to prevent unauthorized SYSTEM-level file writes.

Recommended fix Moderate confidence

Drive Composer >= 2.7.1; Automation Builder >= 2.6.0; Mint Workbench > 5866

  1. 1. Identify which ABB product(s) are installed: Automation Builder, Drive Composer, or Mint Workbench
  2. 2. For Drive Composer: Uninstall current version and install version 2.7.1 or later from ABB's official website or support portal
  3. 3. For Automation Builder: Uninstall current version (1.1.0 to 2.5.0 range) and install version 2.6.0 or later from ABB's official support channels
  4. 4. For Mint Workbench: Uninstall current version (up to 5866) and install a version newer than 5866 from ABB's official support portal
  5. 5. After upgrading, verify the installation completes without errors and confirm the new version number in the application's about or help section
  6. 6. Apply standard least-privilege principles to ensure the application runs with minimal necessary permissions
Caveat Check ABB release notes for your specific product version for any breaking changes or migration requirements before upgrading

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

Fix this in Automation Builder Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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