You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
compliance-remediate.sh writes to fixed /tmp/_cr_jq_err path, which follows a pre-planted symlink #1387
The findings parser opens /tmp/_cr_jq_err with a truncating redirection that follows existing symbolic links. A separate local user can preplant that link and cause the remediator to truncate an unrelated file writable by its account.
Source/control: A lower-privilege local user's filesystem entry at /tmp/_cr_jq_err.
Sink/decision: The stderr redirection opened before jq processes the findings.
Missing mitigation: The stderr destination is neither securely allocated nor protected against following an existing symlink.
Reachability call stack
scripts/compliance-remediate.sh:1019 — main invocation.
scripts/compliance-remediate.sh:903 — validates the findings file and token.
scripts/compliance-remediate.sh:948 — opens /tmp/_cr_jq_err through a truncating shell redirection [sink].
Filed from a CodeRabbit security scan (scan 2d23b5ee-606a-403f-b407-81ddebdb0115, revision 1ea9ee1fbecc). Finding IDs: f1bee4e6-f2fc-4151-8018-f9f6bd665384. CodeRabbit notes that findings relying on its stated assumptions are capped at medium severity; dismiss if an assumption does not hold.
Activity
fix(security): treat repo-derived refs and titles as data in complian…