{"version":"2.1.259","anchor":"bash-path-restriction-checks-now-track-cdpushdpopd-a","canonical_anchor":"bash-path-restriction-checks-now-track-cdpushdpopd-a","heading":"Bash path-restriction checks now track cd \/ pushd \/ popd across compound commands","tier":"notice","area":"Permissions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.259\/e\/bash-path-restriction-checks-now-track-cdpushdpopd-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.259","markdown":"### Bash path-restriction checks now track `cd`\/`pushd`\/`popd` across compound commands\n\nPath deny rules now follow cd, pushd and popd across a compound command, denying reads when a directory target can't be resolved.\n\nBash path-restriction checks now follow directory changes across a compound command. A new walk tracks `cd`, `chdir`, `pushd`, and `popd` (including popping the pushd stack) through a command's statement list, so later commands in the same line are evaluated against deny rules relative to the resolved working directory. If a `cd` target can't be resolved, subsequent reads are denied rather than silently checked against the wrong directory.\n\n- Area: Permissions\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}