CVE-2022-31217
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 · uneditedVulnerabilities 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 confidenceDrive Composer contains vulnerabilities where a low-privileged attacker can create and write files anywhere on the filesystem as SYSTEM, provided the target file does not already exist. Additionally, the installer allows low-privileged users to execute a 'repair' operation, which can be exploited for privilege escalation.
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>= 1.1.0, <= 2.5.0>= 2.0, < 2.7.1<= 5866CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed ABB softwareCheck Program Files for ABB Automation Builder, Drive Composer, or Mint Workbench folders. Look for directories named 'ABB', 'Automation Builder', 'Drive Composer', or 'Mint Workbench' in Program Files or Program Files (x86). Also check the Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for ABB product entries.Affected if One of the three affected ABB products (Automation Builder, Drive Composer, or Mint Workbench) is found installed on the system.
-
Determine installed versionFor Automation Builder: check registry key HKLM\SOFTWARE\ABB\AutomationBuilder\Version or look for version info in the installation directory. For Drive Composer: check Add/Remove Programs or registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for 'Drive Composer' entry. For Mint Workbench: check the Mint Workbench installation folder for a version file or check registry.Affected if The installed version falls within: Automation Builder 1.1.0 through 2.5.0, Drive Composer 2.0 through 2.7.0, or Mint Workbench version 5866 or lower.
-
Verify repair functionality permissionsCheck if non-administrator users have permission to run repair or installer operations. Look for repair executable (often named 'Repair.exe', 'Setup.exe' with repair flag, or similar) in the installation directory and verify file system permissions using icacls or file properties Security tab to see which users/groups can execute it.Affected if Non-privileged users (non-administrators) have execute permissions on repair or installer executables in the ABB software installation directory.
-
Check for SYSTEM service contextExamine Windows services associated with ABB software (look in Services.msc for ABB-related services). Check service properties to see if any run as SYSTEM or LocalSystem account and if the service executable is writable by low-privileged users.Affected if An ABB-related service runs with elevated (SYSTEM) privileges and the service binary or related files are writable by standard users.
A system is affected if it has ABB Automation Builder (1.1.0-2.5.0), Drive Composer (2.0-2.7.0), or Mint Workbench (≤5866) installed AND non-administrative users can access or execute repair/installer functionality, allowing arbitrary file creation or privilege escalation.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2.7.1
Restrict repair/installer operations to administrator accounts only and implement proper privilege validation. Apply vendor patches when available to address the arbitrary file creation vulnerability.
Drive Composer >= 2.7.1; Automation Builder > 2.5.0; Mint Workbench > 5866
- 1. Identify which ABB product(s) in your environment are affected: Automation Builder (versions 1.1.0 through 2.5.0), Drive Composer (versions 2.0 through 2.7.0), or Mint Workbench (version 5866 or earlier)
- 2. For Drive Composer: Upgrade to version 2.7.1 or later by downloading the latest version from the official ABB website or your ABB representative
- 3. For Automation Builder: Upgrade to version 2.5.1 or later if available, or the latest stable release
- 4. For Mint Workbench: Upgrade to a version newer than 5866
- 5. After upgrading, verify the installation completes without errors
- 6. Test that the application functions normally post-upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-31217 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-31217 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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