Description

A security vulnerability has been detected in NellyW8 MCP4EDA 1.0.0. Affected by this vulnerability is an unknown functionality of the component run_openlane/view_waveform. The manipulation of the argument design_name/vcd_file leads to command injection. Local access is required to approach this attack. The project was informed of the problem early through an issue report but has not responded yet.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "5.3",
  "pubDate": "2026-08-09T05:16:51.030Z",
  "pubdate": "2026-08-09T05:16:51.030Z",
  "executiveSummary": "A command injection vulnerability has been identified in NellyW8 MCP4EDA version 1.0.0, specifically within the run_openlane/view_waveform component.\nThe vulnerability allows an authenticated local attacker to execute arbitrary system commands by manipulating the design_name or vcd_file arguments.\nSuccessful exploitation of this flaw can lead to unauthorized execution of system-level commands with the privileges of the application running the affected component, potentially compromising the underlying host environment.\nThe risk implication is rated as critical for local environments, as the integrity and confidentiality of the host system depend entirely on the isolation of this execution context.\nExploitation requires local access to the target system and involves interacting with the vulnerable component through untrusted input passed to the affected arguments.\nThe vendor was notified via an early issue report but has not yet provided an official response or patch to address the vulnerability.",
  "technicalDetails": "The vulnerability resides in the run_openlane/view_waveform component of NellyW8 MCP4EDA 1.0.0, where user-supplied input parameters are improperly sanitized or validated before being passed to an underlying operating system shell or execution function.\nThe root cause is the unsafe handling of parameters associated with the design_name and vcd_file arguments, which are concatenated or evaluated directly within system command execution routines.\nBecause local access is required to approach this attack, an adversary with local shell access or the ability to invoke the application locally can supply a specially crafted payload within the vulnerable arguments.\nThe attack flow proceeds as follows: 1) The user provides malicious input containing shell metacharacters or command separators (such as semicolons, pipes, or backticks) via the design_name or vcd_file parameters; 2) The run_openlane/view_waveform component receives the input without adequate escaping or parameterization; 3) The application constructs a dynamic system command string incorporating the tainted input; 4) The resulting command is executed by the underlying operating system shell; 5) The injected commands execute within the context of the user running the MCP4EDA application.\nThis behavior facilitates arbitrary command execution, enabling the attacker to perform post-exploitation activities such as reading sensitive files, modifying system configurations, or pivoting further into the local environment depending on the privileges assigned to the running process.\nAuthentication requirements depend on the local access controls of the hosting operating system, and no network exposure is inherently required since the attack vector relies on local invocation of the vulnerable component."
}