open/llm-security
1
0
Fork 0
Code Issues Releases 6 Activity

fix(av-surface): no runnable base64-to-shell line on disk

Browse source 
PLAN § v8.1.3 tillegg a. The bash-evasion gallery's T8 comment held a
complete base64-decode-into-shell line whose 16-char blob decodes to a
home-directory deletion, under probe (b)'s 24-char floor. Probe (b2)
found two more of the same shape, fixed here too: the gallery README's
T8 row and tests/e2e/attack-chain.test.mjs (an /etc deletion). Chosen
over an exception list because the gate should have none.

The gallery and the e2e test now encode the blob at runtime from the
same fragments; the README shows a placeholder. Gallery: 10/10 blocked.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Kjell Tore Guttormsen 2026-09-23 11:35:50 +02:00
commit 58d2e8ad8d
Signed by: ktg
SSH key fingerprint: SHA256:JakMjO6FTBBzN0Bhfj9saOoEjaFxlSdYuZQQpM/lF9Q
4 changed files with 12 additions and 8 deletions
Download patch file Download diff file Expand all files Collapse all files

8
examples/bash-evasion-gallery/expected-findings.md
View file

@ -56,7 +56,7 @@ Code 2.1.98+ harness-level checks.
in `expected-findings.md` for documentation; the run script
only checks exit code 2, so it continues to pass after a
rename)
- The base64 blob in T8 (`cm0gLXJmICRIT01F`) decodes to the
literal command. If you change the canonical destructive
target away from `$HOME`, regenerate the blob with
`printf '<new-cmd>' | base64`
- The base64 blob in T8 (`T8_BLOB`) is built at runtime from the
same fragments as the baseline command, so changing the
canonical destructive target updates it too. No runnable
base64-to-shell line is kept on disk (v8.1.3)