Skill instruction executes helper scripts via relative paths from the workspace directory instead of anchoring to the skill root directory.
Rule Explorer
Search the public rule index by CVE, GHSA, CWE, language, framework, author, or rule slug. Filter by language, framework, severity, confidence, license, and validation status.
- Public rules
- 4797
- Downloads
- 10.1M
- Verified
- 4797
- Authors
- 2
Invoking system executables (e.g., taskkill, cmd, powershell) in NSIS without specifying an absolute system directory path (such as '$SYSDIR\') enables binary planting and search path hijacking, potentially leading to local privilege escalation.
Invoking the Graphviz 'dot' binary by bare name or discarding the return value of 'find_binary' can lead to untrusted search path execution (CWE-426 / CWE-427). Ensure the resolved absolute path returned by 'find_binary' is used when executing subprocesses.
Assigning an empty string to an element of `sys.path` (e.g., `sys.path[0] = ""`) instructs Python to include the current working directory (CWD) in its module resolution path. This can lead to local Search Path Hijacking (CWE-426) if the script is executed from an attacker-controlled directory, allowing malicious modules to be imported in place of legitimate
Executing a subprocess with a relative path (e.g., 'cp', 'iptables') rather than an absolute path makes the application vulnerable to Untrusted Search Path (CWE-426) attacks. If the application is run from a directory controlled by an attacker, or if the PATH environment variable is manipulated, an attacker can execute arbitrary binaries, potentially leading
The `LoadLibraryEx` function is used to load DLLs dynamically. Depending on the filepath parameter, the OS version, and the modes set for the process prior to calling LoadLibrary, DLL hijacking may be possible. Attackers can exploit this by placing DLL files with the same name in directories that are searched before the legitimate DLL is. To assist in preven
The `LoadLibrary` function is used to load DLLs dynamically. Depending on the filepath parameter, the OS version, and the modes set for the process prior to calling LoadLibrary, DLL hijacking may be possible. Attackers can exploit this by placing DLL files with the same name in directories that are searched before the legitimate DLL is. To assist in preventi