Skip to content
Fencer Vulns
high 7.8

CVE-2022-31217 json

Drive Composer Link Following Local Privilege Escalation Vulnerability

published 2022-06-15 4 y ago modified 2026-06-17 4 mo ago also EUVD-2022-52801

cvss
7.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.3%
EPSS 0.3% chance of exploitation in 30 days, percentile 26%
public exploits
0
none known

Summary

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.

Patch / fix

  • abb drive_composer 2.7.1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSA-22-202-01 updated cvss 7.8

ABB Drive Composer, Automation Builder, Mint Workbench

  • ABB Automation Builder >= 1.1.0, <= 2.5.0 ABB Drive Composer Entry >= 2.0, <= 2.7 ABB Drive Composer Pro >= 2.0, <= 2.7 ABB Mint Workbench <= 5866
    affected: vendor fix, mitigation “ABB Drive Composer: Update to v2.7.1 or later” new.abb.com

From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
18 mo ago

Exploit prediction

0.33% chance of exploitation in the next 30 days, higher than 26% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 7.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD 3.1 7.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.2 AV:L/AC:L/Au:N/C:C/I:C/A:C

Affected products

  • ABB Drive Composer entry
  • ABB Drive Composer pro
  • ABB ABB Automation Builder
  • ABB Mint WorkBench

Classification

Weakness
  • CWE-59 Improper Link Resolution Before File Access

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.