T05 · Unauthorized Access and Privilege Escalation
- Location
scripts/comfyui_skill.py:65- Finding
Unsafe Guidance to Elevate Privileges and Disable Antivirus Protection
- Content
View full analysis
Vulnerability Details
File Location:
scripts/comfyui_skill.py:65,scripts/comfyui_skill.py:254, andSKILL.md:89
Vulnerability Type: Least-privilege violation and unsafe security-control guidance
Risk Level: MediumVulnerable Code
scripts/comfyui_skill.py:65:python result.append("💡 修复:安装.NET框架、以管理员运行、检查路径无中文/空格")scripts/comfyui_skill.py:254:python "启动闪退": ["安装 .NET Framework 4.8+", "以管理员身份运行", "检查路径不包含中文/空格", "关闭杀毒软件误报"],SKILL.md:89:markdown | 启动闪退 | 安装 .NET Framework 4.8+、以管理员运行、检查路径无中文/空格 |Technical Analysis
The troubleshooting instructions recommend running ComfyUI components as an administrator and, in the script, disabling antivirus protection. These recommendations are presented without first determining whether elevated privileges are required, verifying the provenance of the selected ComfyUI bundle, or limiting the elevation to a specific trusted operation.
The skill accepts a configurable ComfyUI installation path and launches executables or batch files from that directory. Although the skill does not programmatically elevate privileges or disable antivirus, its guidance can persuade a user to apply those actions to an untrusted or compromised bundle. Running such components as an administrator breaks the principle of least privilege, while disabling antivirus weakens a security boundary that might otherwise detect malicious executables, plugins, or scripts.
Attack Path
- An attacker distributes or modifies a ComfyUI bundle containing a malicious launcher, startup batch file, executable, or plugin.
- The victim configures the skill to use that bundle or places it at the expected path.
- The malicious or incompatible component causes startup to fail, or deliberately displays symptoms resembling a startup crash.
- The skill recommends running the bundle as an administrator and may recommend disabling antivirus protection.
...[truncated 1268 chars]
- Remediation
View remediation
Remediation Suggestions
- Remove blanket recommendations to run ComfyUI as an administrator or disable antivirus protection.
- Keep ComfyUI and its launcher running under a standard user account by default.
- Diagnose the actual failure before suggesting permission changes, including checking file permissions, dependency availability, logs, path validity, and whether the executable is blocked.
- If a narrowly scoped operation genuinely requires elevation, identify that exact operation and explain why it requires additional privileges. Do not elevate the entire launcher or plugin ecosystem.
- Require users to verify the source, signature, checksum, and integrity of the ComfyUI bundle before executing its components.
- Never recommend disabling antivirus globally. For a verified false positive, direct users to submit the file for analysis and, only when necessary, create the narrowest possible file-specific exclusion for a verified artifact.
- Add an explicit warning that launchers, batch files, custom nodes, and plugins are executable code and must not be elevated unless their provenance has been independently verified.
- Replace the affected troubleshooting text with safe guidance such as reviewing launcher logs, restoring quarantined files only after verification, and correcting directory permissions without granting unnecessary system-wide privileges.
