T05 · Unauthorized Access and Privilege Escalation
Warning
- Location
SKILL.md:89- Finding
Unrestricted Out-of-Repository File Reads Through Manifest Paths
- Content
View full analysis
/dev/null) \ || REF=$(git -C $S for-each-ref --format='%(refname:short)' refs/remotes | head -1) # No REF at all? The sibling has no remote-tracking ref. Report UNVERIFIED. git -C $S show "$REF:index.html" # the value git -C $S log -1 --format=%cs "$REF" # its as-of date ``` Every command above reads local refs and makes no network call. Quote the as-of date next to the value: a remote-tracking ref is a local mirror and can lag the real remote, and a value whose as-of date you can't state is not a fresh value. Report divergence between the sibling's working tree and that ref as a finding. Do **not** fetch, pull, rebase, checkout, or commit in a repo you are only auditing. `git fetch` is not exempt: it writes the sibling's remote-tracking refs, `FETCH_HEAD`, and packfiles, and makes an unsolicited network call on the user's behalf. `git pull` additionally moves the sibling's working tree, which can clobber uncommitted work. If you cannot establish a value read-only — no remote-tracking ref on disk, or the file is absent from it — report the fact as **UNVERIFIED** ...[truncated 3602 chars]- Remediation
View remediation