openscad

Fail

Audited by Gen Agent Trust Hub on Sep 13, 2026

Risk Level: HIGHDYNAMIC_EXECUTIONCOMMAND_EXECUTION
Full Analysis
  • [DYNAMIC_EXECUTION]: The scripts scripts/validate.js and scripts/test-design.js utilize the eval() function within their extractParameters methods to parse variable values from .scad files. This pattern is highly insecure as it allows for arbitrary JavaScript code execution if a processed OpenSCAD file contains malicious payloads within its parameter assignments (e.g., value = (function(){ /* malicious code */ })();). Since the agent is instructed to run these scripts on files in the workspace, this represents a significant Remote Code Execution (RCE) vector.
  • [COMMAND_EXECUTION]: Multiple utility scripts, including scripts/analyze-geometry.js, scripts/check-bed-fit.js, scripts/test-design.js, and scripts/validate.js, execute the openscad binary using execSync. These scripts pass file paths and parameter values directly into the shell command string. While they attempt to use quotes, the reliance on external file content to build command arguments creates a risk of command injection if the input files contain specially crafted filenames or parameter strings designed to break out of the shell quoting context.
Recommendations
  • AI detected serious security threats
Audit Metadata
Risk Level
HIGH
Analyzed
Sep 13, 2026, 11:22 PM