Description

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in ABB Mint Workbench I. This issue affects Mint Workbench I: through 5876.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "7.5",
  "pubDate": "2026-09-23T06:17:01.310Z",
  "pubdate": "2026-09-23T06:17:01.310Z",
  "executiveSummary": "The ABB Mint Workbench I application is susceptible to an Improper Limitation of a Pathname to a Restricted Directory vulnerability, classified as Path Traversal (CWE-22).\nThis vulnerability exists within versions up to and including 5876, allowing an attacker to manipulate file path references.\nThe primary impact involves unauthorized access to sensitive files residing outside the intended application directory, potentially leading to information disclosure or system compromise.\nThe vulnerability is exploitable by an attacker who can influence the input parameters processed by the application's file handling mechanisms.\nSuccessful exploitation allows an attacker to traverse the directory structure and access unauthorized resources that should be restricted based on the application's security configuration.\nDue to the nature of the software, this flaw poses a significant risk to the integrity and confidentiality of the host system, particularly in industrial or engineering environments where Mint Workbench is deployed.",
  "technicalDetails": "The vulnerability originates from the improper validation and sanitization of user-supplied input used to construct file paths within Mint Workbench I (up to version 5876).\nSpecifically, the application fails to adequately restrict path navigation, allowing characters such as dot-dot-slash ('../') sequences to be processed by file system APIs.\nWhen an application accepts a user-provided file path without enforcing strict directory boundaries, an attacker can supply crafted input to escape the root directory context and access arbitrary files on the underlying operating system.\nThe attack flow involves an adversary intercepting or crafting requests sent to the affected component of the Mint Workbench software. By injecting malicious path sequences into the input vector, the attacker forces the application to resolve a path that exists outside the designated directory structure.\nOnce the application resolves the manipulated path, it performs file operations—such as read or open—on the requested resource, effectively returning or acting upon data that the attacker is not authorized to access.\nThe vulnerability leverages the inherent trust the application places in input parameters regarding file access. Because there is insufficient logical checking to ensure the final resolved path is contained within the authorized perimeter, the file system enforces access based on the privileges of the user running the Mint Workbench service.\nIn scenarios where the application runs with elevated system privileges, the impact of this path traversal is compounded, as the attacker may gain read access to critical system configuration files, sensitive project data, or authentication artifacts.\nThe attack does not necessarily require advanced exploitation techniques, such as memory corruption or buffer overflows; rather, it relies on the application's misuse of file system APIs to handle user-controlled path strings.\nThe absence of a robust canonicalization process—which would resolve paths to their absolute, unambiguous forms and verify their location against an allow-list—allows the traversal to succeed, resulting in unauthorized data exposure."
}