{"version":"2.1.213","anchor":"shell-safety-improved-redirect-analysis","canonical_anchor":"shell-safety-improved-redirect-analysis","heading":"Shell Safety: Improved Redirect Analysis","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.213\/e\/shell-safety-improved-redirect-analysis","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.213","markdown":"### Shell Safety: Improved Redirect Analysis\n\n**What**\n\nThe Bash parser now validates redirect nodes for additional dangerous patterns that could hide behavior from the safety classifier.\n\nNew cases detected:\n\n- `fd-variable assignment` \u2014 a redirect that uses a shell variable (`{var}>`) as the file descriptor; this modifies the variable as a side effect\n- `close-fd redirect followed by a word` \u2014 `>&-` or `<&-` followed by text that bash would pass as a hidden argument to the command\n- `redirect target starting with -` after `>&` or `<&` \u2014 bash treats the dash as a close-fd operator and passes the remainder as an argument\n\n**Evidence**\n\nRedirect analysis (search for `\"Redirect uses\"`, `\"fd-variable assignment\"`, `\"Close-fd redirect is followed by a word\"`)"}