--- name: security-triage-b4f7ebf74247 description: Triage GitHub security advisories for OpenClaw with high-confidence close/keep decisions, exact tag and commit verification, trust-model checks, optional hardening notes, and a final reply ready to post and copy to clipboard. --- # Security Triage Use when reviewing OpenClaw security advisories, drafts, or GHSA reports. Goal: high-confidence maintainers' triage without over-closing real issues or shipping unnecessary regressions. ## Close Bar Close only if one of these is true: - duplicate of an existing advisory or fixed issue - invalid against shipped behavior - out of scope under `SECURITY.md` - fixed before any affected release/tag Do not close only because `main` is fixed. If latest shipped tag or npm release is affected, keep it open until released or published with the right status. ## Required Reads Before answering: 1. Read `SECURITY.md`. 2. Read the GHSA body with `gh api /repos/openclaw/openclaw/security-advisories/`. 3. Inspect the exact implicated code paths. 4. Verify shipped state: - `git tag --sort=-creatordate | head` - `npm view openclaw version --userconfig "$(mktemp)"` - `git tag --contains ` - if needed: `git show :path/to/file` 5. Search for canonical overlap: - existing published GHSAs - older fixed bugs - same trust-model class already covered in `SECURITY.md` ## Review Method For each advisory, decide: - `close` - `keep open` - `keep open but narrow` Check in this order: 1. Trust model - Is the prerequisite already inside trusted host/local/plugin/operator state? - Does `SECURITY.md` explicitly call this class out as out of scope or hardening-only? 2. Shipped behavior - Is the bug present in the latest shipped tag or npm release? - Was it fixed before release? 3. Exploit path - Does the report show a real boundary bypass, not just prompt injection, local same-user control, or helper-level semantics? 4. Functional tradeoff - If a hardening change would reduce intended user functionality, call that out before proposing it. - Prefer fixes that preserve user workflows over deny-by-default regressions unless the boundary demands it. ## Response Format When preparing a maintainer-ready close reply: 1. Print the GHSA URL first. 2. Then draft a detailed response the maintainer can post. 3. Include: - exact reason for close - exact code refs - exact shipped tag / release facts - exact fix commit or canonical duplicate GHSA when applicable - optional hardening note only if worthwhile and functionality-preserving Keep tone firm, specific, non-defensive. ## Clipboard Step After drafting the final post body, copy it: ```bash pbcopy <<'EOF' EOF ``` Tell the user that the clipboard now contains the proposed response. ## Useful Commands ```bash gh api /repos/openclaw/openclaw/security-advisories/ gh api /repos/openclaw/openclaw/security-advisories --paginate git tag --sort=-creatordate | head -n 20 npm view openclaw version --userconfig "$(mktemp)" git tag --contains git show : gh search issues --repo openclaw/openclaw --match title,body,comments -- "" gh search prs --repo openclaw/openclaw --match title,body,comments -- "" ``` ## Decision Notes - “fixed on main, unreleased” is usually not a close. - “needs attacker-controlled trusted local state first” is usually out of scope. - “same-host same-user process can already read/write local state” is usually out of scope. - “helper function behaves differently than documented config semantics” is usually invalid. - If only the severity is wrong but the bug is real, keep it open and narrow the impact in the reply. --- Source attribution: eszxcvfd Original project: https://github.com/eszxcvfd/openclaw-team/blob/2c098f9d857dcb3eabfeed97371492fb89121d7a/openclaw/.agents/skills/security-triage/SKILL.md License: MIT License information: https://opensource.org/license/mit Original upstream instructions; downloaded from Dave AI. ## Upstream license notice MIT License Copyright (c) 2025 Peter Steinberger Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. # Dave AI resource metadata Creator / publisher: eszxcvfd Original project: https://github.com/eszxcvfd/openclaw-team/blob/2c098f9d857dcb3eabfeed97371492fb89121d7a/openclaw/.agents/skills/security-triage/SKILL.md Attribution basis: Source repository record Fields of work: Development & Engineering Roles: Backend Developer, Security Engineer Specialties: Backend Tools: GitHub Country applicability: Country not specified Classification basis: Source catalog labels Instruction SHA-256: 3787b7d01ffbdbf78bda47c591a40a43cfc1506198c5cac57ad29d939628c69a