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

fix(llm-security): misc scanner correctness — reflog FP, diff exact-pass, hex dedupe, SARIF version (#20,#22,#50,#54,#56)

Browse source 
#20 git-forensics' reflog force-push detector had a redundant bare 'reset' term subsuming 'reset:', so any commit subject containing 'reset' tripped it; removed. #22 diff-engine's per-current moved-fallback greedily consumed a baseline candidate a later byte-exact match needed (mislabeling unchanged as new/moved on duplicate fingerprints); a global exact pass now runs before the moved-fallback. #54 memory-poisoning double-reported a 64+ char hex token as both base64 and hex; the base64 check now skips pure-hex tokens.

#56 SARIF output hardcoded driver.version 6.0.0 because the orchestrator called toSARIF() without a version; it now passes the real plugin version from package.json. #50 the VS Code known-malicious blocklist was empty with no explanation (unlike the JetBrains file's 'empty by design' note); added a matching blocklist_note. Suite 2004/0.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Claude-Session: https://claude.ai/code/session_01TcQyMTQfyrsAapaCMPxTtQ
This commit is contained in:
Kjell Tore Guttormsen 2026-07-18 10:36:51 +02:00
commit 66e8ce2740
10 changed files with 340 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

4
scanners/memory-poisoning-scanner.mjs
View file

@ -326,6 +326,10 @@ function detectEncodedPayloads(content, relPath) {
BASE64_TOKEN_RE.lastIndex = 0;
let match;
while ((match = BASE64_TOKEN_RE.exec(line)) !== null) {
// v7.8.3 (#54): a 64+ char pure-hex token (e.g. a sha256) is also
// reported by the hex-blob check below — skip the base64 report so one
// token yields one finding, labelled hex.
if (/^(?:0x)?[0-9a-fA-F]{64,}$/.test(match[0])) continue;
if (isBase64Like(match[0])) {
results.push(finding({
scanner: 'MEM',