destructive_command_guard: dcg: Exponential-time command-substitution preprocessing lets a crafted command hang dcg and bypass the guard via hook-timeout fail-open
What fixes it
- 0.6.6destructive_command_guard (dcg), otherGitHub
A fixed version on one release line is not the upgrade target for every line. Check your exact version and any vendor backports.
Description
destructive_command_guard (dcg) is a command-line safety tool that blocks destructive shell commands before AI coding agents run them. Prior to 0.6.6, nested or unclosed substitutions are recursively rescanned after an inner scan returns unterminated, producing exponential-time work. The affected scanners are reached through split_command_segments in src/packs/mod.rs. a destructive command followed by nested or unclosed $( or $(( sequences. nested or unclosed $( and $(( sequences cause repeated rescanning of the remaining command suffix. a hung PreToolUse hook fails open, allowing the destructive command to proceed. This issue is fixed in version 0.6.6.
Text from CVE List
Affected versions 2
- destructive_command_guardaffected: < 0.6.6CVE List
- destructive_command_guard (dcg), other< 0.6.6GitHub
References 4
- github.com/Dicklesworthstone/destructive_command_guard/commit/ba16bdd074b045329dc0ca6ec9a08c44403cfe1bFixvia CVE List
- github.com/Dicklesworthstone/destructive_command_guard/releases/tag/v0.6.6Fixvia CVE List
- github.com/Dicklesworthstone/destructive_command_guard/security/advisories/GHSA-4cfr-w3v5-w5j5Advisoryvia CVE List
- github.com/Dicklesworthstone/destructive_command_guard/issues/189Referencevia CVE List