dbcve.org
Automation BuilderApplication · Abb

CVE-2022-31218

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

Drive Composer contains a privilege escalation vulnerability where the installer repair operation allows a low-privileged local attacker to create arbitrary files anywhere on the filesystem with SYSTEM-level privileges. The attack is limited to creating new files (not overwriting existing ones), but combined with other techniques could lead to full system compromise.

MitigationApply vendor patches or updates for Drive Composer as soon as available; in the interim, restrict or monitor access to the repair functionality and limit low-privileged users' ability to execute installer operations.

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 Windows registry or Program Files for ABB Drive Composer, ABB Automation Builder, or ABB Mint Workbench installations
    Affected if Any of these ABB products are installed on the system
  2. Determine Drive Composer version
    Locate Drive Composer in the system (commonly in Program Files) and check the installed version from the application's properties or About dialog
    Affected if Version is >= 2.0 and < 2.7.1
  3. Determine Automation Builder version
    Check Automation Builder installation properties or version information in the application directory
    Affected if Version is >= 1.1.0 and <= 2.5.0 (this version range includes Drive Composer)
  4. Determine Mint Workbench version
    Check Mint Workbench installation properties or version information
    Affected if Version is <= 5866
  5. Verify if installer repair functionality exists
    Locate the installer executable or repair functionality for the installed ABB product - check for setup.exe, installer, or repair options in the installation directory
    Affected if The installer repair operation is present and accessible to low-privileged users

The system is affected if any of these products are installed with the specified vulnerable version ranges AND the installer repair functionality is accessible to the user checking the system.

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

Apply vendor patches or updates for Drive Composer as soon as available; in the interim, restrict or monitor access to the repair functionality and limit low-privileged users' ability to execute installer operations.

Recommended fix Moderate confidence

Drive Composer 2.7.1+; Automation Builder 2.6.0+; Mint Workbench 5867+

  1. Verify current installed version of Drive Composer, Automation Builder, or Mint Workbench
  2. For Drive Composer: Upgrade to version 2.7.1 or later
  3. For Automation Builder: Upgrade to version 2.6.0 or later
  4. For Mint Workbench: Upgrade to version 5867 or later
  5. After upgrade, verify the symlink vulnerability is resolved by confirming the repair operation no longer allows arbitrary file creation

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

Fix this in Automation Builder Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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