dbcve.org
Mint WorkbenchApplication · Abb

CVE-2024-5402

HIGH · 7.8 CVSS v3.1 Published 2024-07-15
Fix available
A fix is available. Upgrade to after 5868 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
Unquoted Search Path or Element vulnerability in ABB Mint Workbench. A local attacker who successfully exploited this vulnerability could gain elevated privileges by inserting an executable file in the path of the affected service. This issue affects Mint Workbench I versions: from 5866 before 5868.

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

This is an unquoted service path vulnerability in ABB Mint Workbench where the service executable path contains spaces and is not properly quoted. A local attacker with write access to an intermediate directory in the path can place a malicious executable that will be executed with elevated (system) privileges when the service restarts.

MitigationUpgrade ABB Mint Workbench to version 5868 or later to obtain the patched binary with properly quoted service paths.

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
Mint WorkbenchApplication
Affected:>= 5866, <= 5868

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 if ABB Mint Workbench is installed
    Check for the presence of ABB Mint Workbench installation directory, typically found in Program Files or Program Files (x86). Look for Mint Workbench executable or service-related files.
    Affected if ABB Mint Workbench is found on the system
  2. Determine installed version
    Locate the Mint Workbench version information, typically available in the application properties, installer logs, or the executable metadata.
    Affected if Version is 5866, 5867, or 5868
  3. Check Windows service configuration
    Use Windows command 'sc qc' or 'sc query' to query the Mint Workbench service. Retrieve the BINARY_PATH_NAME field which contains the executable path.
    Affected if A service named Mint Workbench exists and the BINARY_PATH_NAME field contains an unquoted path with spaces
  4. Identify intermediate directories in service path
    Parse the service binary path to identify all directories between the drive letter and the executable filename. Check each directory for write permissions.
    Affected if Any intermediate directory in the service path is writable by the current user

The system is affected if ABB Mint Workbench version 5866-5868 is installed, has a Windows service with an unquoted path containing spaces, and any directory in that path is writable.

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 a release after 5868
Interim mitigation

Upgrade ABB Mint Workbench to version 5868 or later to obtain the patched binary with properly quoted service paths.

Recommended fix Moderate confidence

ABB Mint Workbench version 5868 or later

  1. 1. Identify the current installed version of ABB Mint Workbench by checking the application or system information
  2. 2. Navigate to the official ABB software download portal or contact ABB support to obtain version 5868 or later
  3. 3. Before upgrading, back up any critical project files and configurations associated with Mint Workbench
  4. 4. Run the installer for the new version (5868 or higher) with administrative privileges
  5. 5. Follow the installation wizard prompts to complete the upgrade
  6. 6. After installation, verify the new version number matches the expected fixed release
  7. 7. Restart the Mint Workbench application and confirm normal operation
Caveat Review ABB release notes for version 5868 to check for any compatibility changes with existing projects or integrations

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

Fix this in Mint Workbench Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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