어떤 스킬인가요?
로그인 기능이나 파일 업로드를 바꾼 뒤 놓친 위험이 없는지 검토할 때 활용합니다. 문자열 하나를 보고 위험하다고 단정하기보다 사용자 입력이 실제로 어디까지 전달되는지 추적합니다.
대상 코드와 접근 권한, 이미 적용한 보호 장치를 함께 알려주세요. 발생 조건과 영향, 확인 수준을 구분한 결과를 받을 수 있습니다. 자동 점검이 서비스 전체의 안전을 보증하지는 않으므로 중요한 변경은 테스트와 별도 검토를 함께 진행합니다.
security-review · 스킬 지원 에이전트
입력 검증, 인증·권한과 민감정보 처리를 보며 근거가 있는 보안 문제를 정리합니다.
로그인 기능이나 파일 업로드를 바꾼 뒤 놓친 위험이 없는지 검토할 때 활용합니다. 문자열 하나를 보고 위험하다고 단정하기보다 사용자 입력이 실제로 어디까지 전달되는지 추적합니다.
대상 코드와 접근 권한, 이미 적용한 보호 장치를 함께 알려주세요. 발생 조건과 영향, 확인 수준을 구분한 결과를 받을 수 있습니다. 자동 점검이 서비스 전체의 안전을 보증하지는 않으므로 중요한 변경은 테스트와 별도 검토를 함께 진행합니다.
security-review로 이 로그인과 파일 업로드 코드를 검토해줘. 권한 우회·입력 처리·민감정보 노출을 중심으로 경로와 근거를 적고 수정 방향을 제안해줘.
받을 수 있는 결과취약점 후보와 근거·수정 방향
2026-10-05 두 줄의 격리 예제를 수동 검토했습니다. 브라우저 공격 실행이나 운영 사이트 보안 진단은 수행하지 않았습니다.
이 예제는 URL의 name 값을 읽어 화면에 넣습니다. 검토할 부분은 값의 출처와 삽입 방식입니다. 전체 두 줄을 확인했을 때 별도의 정제 과정이 없었고, 입력을 HTML로 해석하는 innerHTML에 전달하고 있었습니다.
const value = new URLSearchParams(location.search).get("name");
document.querySelector("#name").innerHTML = value;이름을 글자로 보여주려는 경우에는 HTML 해석이 필요하지 않습니다. textContent로 바꾸면 값을 텍스트로 넣습니다. HTML 편집기를 만드는 경우에는 요구사항이 다르므로 같은 수정안을 그대로 적용할 수 없습니다.
document.querySelector("#name").textContent = value || "";확인한 것은 이 작은 코드의 입력 흐름과 위험한 삽입 방식입니다. 실제 앱의 로그인, 저장소, 서버 API까지 검토한 것은 아닙니다. 스킬에 변경 파일뿐 아니라 입력을 만드는 코드와 주변 설정도 주고, 발견 사항마다 재현 조건을 설명해달라고 요청하세요.
스킬 지원 에이전트와 코드 접근이 필요합니다. 운영 환경 공격 실행은 별도 승인 범위이며 이 소개의 사용 예시는 코드 검토입니다.
현재 사용 중인 스킬 지원 에이전트에 아래 요청을 붙여넣으세요. SKILL.md만 복사하면 보조 파일이 빠질 수 있어요.
https://github.com/getsentry/skills 에서 skills/security-review 스킬을 현재 에이전트의 스킬 폴더에 설치해줘. SKILL.md와 이 스킬이 참조하는 scripts·references·assets와 공통 파일을 함께 유지하고, 필요한 실행 환경과 추가 연결을 확인한 뒤 알려줘. 설치가 끝나면 security-review 스킬을 인식하는지 확인해줘.
“security-review 스킬을 사용해줘. 입력 자료: 코드·인증 흐름·입력 경로”처럼 요청하세요. 위의 예시를 내 자료에 맞게 바꿔도 좋아요.
예상 결과는 ‘취약점 후보와 근거·수정 방향’입니다. 필요한 내용이 포함됐는지 확인하세요. 입력 자료의 사실·숫자와 결과를 대조하고, 부족한 부분을 이어서 요청하세요.
제작자 원본 2026-10-04 확인 · 설치 안내 2026-10-04 확인 · 격리 폴더 설치·샘플 검토 2026-10-05 확인 · 에이전트 자동 호출 미검증
모델 사용 요금과 연결 앱 요금은 이용 중인 서비스의 정책을 따릅니다.
설치 안내 출처--- name: security-review description: Security code review for vulnerabilities. Use when asked to "security review", "find vulnerabilities", "check for security issues", "audit security", "OWASP review", or review code for injection, XSS, authentication, authorization, cryptography issues. Provides systematic review with confidence-based reporting. allowed-tools: Read Grep Glob Bash Task license: LICENSE --- <!-- Reference material based on OWASP Cheat Sheet Series (CC BY-SA 4.0) https://cheatsheetseries.owasp.org/ --> # Security Review Skill Identify exploitable security vulnerabilities in code. Report only **HIGH CONFIDENCE** findings—clear vulnerable patterns with attacker-controlled input. ## Scope: Research vs. Reporting **CRITICAL DISTINCTION:** - **Report on**: Only the specific file, diff, or code provided by the user - **Research**: The ENTIRE codebase to build confidence before reporting Before flagging any issue, you MUST research the codebase to understand: - Where does this input actually come from? (Trace data flow)--- name: security-review description: Security code review for vulnerabilities. Use when asked to "security review", "find vulnerabilities", "check for security issues", "audit security", "OWASP review", or review code for injection, XSS, authentication, authorization, cryptography issues. Provides systematic review with confidence-based reporting. allowed-tools: Read Grep Glob Bash Task license: LICENSE --- <!-- Reference material based on OWASP Cheat Sheet Series (CC BY-SA 4.0) https://cheatsheetseries.owasp.org/ --> # Security Review Skill Identify exploitable security vulnerabilities in code. Report only **HIGH CONFIDENCE** findings—clear vulnerable patterns with attacker-controlled input. ## Scope: Research vs. Reporting **CRITICAL DISTINCTION:** - **Report on**: Only the specific file, diff, or code provided by the user - **Research**: The ENTIRE codebase to build confidence before reporting Before flagging any issue, you MUST research the codebase to understand: - Where does this input actually come from? (Trace data flow) - Is there validation/sanitization elsewhere? - How is this configured? (Check settings, config files, middleware) - What framework protections exist? **Do NOT report issues based solely on pattern matching.** Investigate first, then report only what you're confident is exploitable. ## Confidence Levels | Level | Criteria | Action | |-------|----------|--------| | **HIGH** | Vulnerable pattern + attacker-controlled input confirmed | **Report** with severity | | **MEDIUM** | Vulnerable pattern, input source unclear | **Note** as "Needs verification" | | **LOW** | Theoretical, best practice, defense-in-depth | **Do not report** | ## Do Not Flag ### General Rules - Test files (unless explicitly reviewing test security) - Dead code, commented code, documentation strings - Patterns using **constants** or **server-controlled configuration** - Code paths that require prior authentication to reach (note the auth requirement instead) ### Server-Controlled Values (NOT Attacker-Controlled) These are configured by operators, not controlled by attackers: | Source | Example | Why It's Safe | |--------|---------|---------------| | Django settings | `settings.API_URL`, `settings.ALLOWED_HOSTS` | Set via config/env at deployment | | Environment variables | `os.environ.get('DATABASE_URL')` | Deployment configuration | | Config files | `config.yaml`, `app.config['KEY']` | Server-side files | | Framework constants | `django.conf.settings.*` | Not user-modifiable | | Hardcoded values | `BASE_URL = "https://api.internal"` | Compile-time constants | **SSRF Example - NOT a vulnerability:** ```python # SAFE: URL comes from Django settings (server-controlled) response = requests.get(f"{settings.SEER_AUTOFIX_URL}{path}") ``` **SSRF Example - IS a vulnerability:** ```python # VULNERABLE: URL comes from request (attacker-controlled) response = requests.get(request.GET.get('url')) ``` ### Framework-Mitigated Patterns Check language guides before flagging. Common false positives: | Pattern | Why It's Usually Safe | |---------|----------------------| | Django `{{ variable }}` | Auto-escaped by default | | React `{variable}` | Auto-escaped by default | | Vue `{{ variable }}` | Auto-escaped by default | | `User.objects.filter(id=input)` | ORM parameterizes queries | | `cursor.execute("...%s", (input,))` | Parameterized query | | `innerHTML = "<b>Loading...</b>"` | Constant string, no user input | **Only flag these when:** - Django: `{{ var|safe }}`, `{% autoescape off %}`, `mark_safe(user_input)` - React: `dangerouslySetInnerHTML={{__html: userInput}}` - Vue: `v-html="userInput"` - ORM: `.raw()`, `.extra()`, `RawSQL()` with string interpolation ## Review Process ### 1. Detect Context What type of code am I reviewing? | Code Type | Load These References | |-----------|----------------------| | API endpoints, routes | `authorization.md`, `authentication.md`, `injection.md` | | Frontend, templates | `xss.md`, `csrf.md` | | File handling, uploads | `file-security.md` | | Crypto, secrets, tokens | `cryptography.md`, `data-protection.md` | | Data serialization | `deserialization.md` | | External requests | `ssrf.md` | | Business workflows | `business-logic.md` | | GraphQL, REST design | `api-security.md` | | Config, headers, CORS | `misconfiguration.md` | | CI/CD, dependencies | `supply-chain.md` | | Error handling | `error-handling.md` | | Audit, logging | `logging.md` | ### 2. Load Language Guide Based on file extension or imports: | Indicators | Guide | |------------|-------| | `.py`, `django`, `flask`, `fastapi` | `languages/python.md` | | `.js`, `.ts`, `express`, `react`, `vue`, `next` | `languages/javascript.md` | | `.go`, `go.mod` | `languages/go.md` | | `.rs`, `Cargo.toml` | `languages/rust.md` | | `.java`, `spring`, `@Controller` | `languages/java.md` | ### 3. Load Infrastructure Guide (if applicable) | File Type | Guide | |-----------|-------| | `Dockerfile`, `.dockerignore` | `infrastructure/docker.md` | | K8s manifests, Helm charts | `infrastructure/kubernetes.md` | | `.tf`, Terraform | `infrastructure/terraform.md` | | GitHub Actions, `.gitlab-ci.yml` | `infrastructure/ci-cd.md` | | AWS/GCP/Azure configs, IAM | `infrastructure/cloud.md` | ### 4. Research Before Flagging **For each potential issue, research the codebase to build confidence:** - Where does this value actually come from? Trace the data flow. - Is it configured at deployment (settings, env vars) or from user input? - Is there validation, sanitization, or allowlisting elsewhere? - What framework protections apply? Only report issues where you have HIGH confidence after understanding the broader context. ### 5. Verify Exploitability For each potential finding, confirm: **Is the input attacker-controlled?** | Attacker-Controlled (Investigate) | Server-Controlled (Usually Safe) | |-----------------------------------|----------------------------------| | `request.GET`, `request.POST`, `request.args` | `settings.X`, `app.config['X']` | | `request.json`, `request.data`, `request.body` | `os.environ.get('X')` | | `request.headers` (most headers) | Hardcoded constants | | `request.cookies` (unsigned) | Internal service URLs from config | | URL path segments: `/users/<id>/` | Database content from admin/system | | File uploads (content and names) | Signed session data | | Database content from other users | Framework settings | | WebSocket messages | | **Does the framework mitigate this?** - Check language guide for auto-escaping, parameterization - Check for middleware/decorators that sanitize **Is there validation upstream?** - Input validation before this code - Sanitization libraries (DOMPurify, bleach, etc.) ### 6. Report HIGH Confidence Only Skip theoretical issues. Report only what you've confirmed is exploitable after research. --- ## Severity Classification | Severity | Impact | Examples | |----------|--------|----------| | **Critical** | Direct exploit, severe impact, no auth required | RCE, SQL injection to data, auth bypass, hardcoded secrets | | **High** | Exploitable with conditions, significant impact | Stored XSS, SSRF to metadata, IDOR to sensitive data | | **Medium** | Specific conditions required, moderate impact | Reflected XSS, CSRF on state-changing actions, path traversal | | **Low** | Defense-in-depth, minimal direct impact | Missing headers, verbose errors, weak algorithms in non-critical context | --- ## Quick Patterns Reference ### Always Flag (Critical) ``` eval(user_input) # Any language exec(user_input) # Any language pickle.loads(user_data) # Python yaml.load(user_data) # Python (not safe_load) unserialize($user_data) # PHP deserialize(user_data) # Java ObjectInputStream shell=True + user_input # Python subprocess child_process.exec(user) # Node.js ``` ### Always Flag (High) ``` innerHTML = userInput # DOM XSS dangerouslySetInnerHTML={user} # React XSS v-html="userInput" # Vue XSS f"SELECT * FROM x WHERE {user}" # SQL injection `SELECT * FROM x WHERE ${user}` # SQL injection os.system(f"cmd {user_input}") # Command injection ``` ### Always Flag (Secrets) ``` password = "hardcoded" api_key = "sk-..." AWS_SECRET_ACCESS_KEY = "..." private_key = "-----BEGIN" ``` ### Check Context First (MUST Investigate Before Flagging) ``` # SSRF - ONLY if URL is from user input, NOT from settings/config requests.get(request.GET['url']) # FLAG: User-controlled URL requests.get(settings.API_URL) # SAFE: Server-controlled config requests.get(f"{settings.BASE}/{x}") # CHECK: Is 'x' user input? # Path traversal - ONLY if path is from user input open(request.GET['file']) # FLAG: User-controlled path open(settings.LOG_PATH) # SAFE: Server-controlled config open(f"{BASE_DIR}/{filename}") # CHECK: Is 'filename' user input? # Open redirect - ONLY if URL is from user input redirect(request.GET['next']) # FLAG: User-controlled redirect redirect(settings.LOGIN_URL) # SAFE: Server-controlled config # Weak crypto - ONLY if used for security purposes hashlib.md5(file_content) # SAFE: File checksums, caching hashlib.md5(password) # FLAG: Password hashing random.random() # SAFE: Non-security uses (UI, sampling) random.random() for token # FLAG: Security tokens need secrets module ``` --- ## Output Format ```markdown ## Security Review: [File/Component Name] ### Summary - **Findings**: X (Y Critical, Z High, ...) - **Risk Level**: Critical/High/Medium/Low - **Confidence**: High/Mixed ### Findings #### [VULN-001] [Vulnerability Type] (Severity) - **Location**: `file.py:123` - **Confidence**: High - **Issue**: [What the vulnerability is] - **Impact**: [What an attacker could do] - **Evidence**: ```python [Vulnerable code snippet] ``` - **Fix**: [How to remediate] ### Needs Verification #### [VERIFY-001] [Potential Issue] - **Location**: `file.py:456` - **Question**: [What needs to be verified] ``` If no vulnerabilities found, state: "No high-confidence vulnerabilities identified." --- ## Reference Files ### Core Vulnerabilities (`references/`) | File | Covers | |------|--------| | `injection.md` | SQL, NoSQL, OS command, LDAP, template injection | | `xss.md` | Reflected, stored, DOM-based XSS | | `authorization.md` | Authorization, IDOR, privilege escalation | | `authentication.md` | Sessions, credentials, password storage | | `cryptography.md` | Algorithms, key management, randomness | | `deserialization.md` | Pickle, YAML, Java, PHP deserialization | | `file-security.md` | Path traversal, uploads, XXE | | `ssrf.md` | Server-side request forgery | | `csrf.md` | Cross-site request forgery | | `data-protection.md` | Secrets exposure, PII, logging | | `api-security.md` | REST, GraphQL, mass assignment | | `business-logic.md` | Race conditions, workflow bypass | | `modern-threats.md` | Prototype pollution, LLM injection, WebSocket | | `misconfiguration.md` | Headers, CORS, debug mode, defaults | | `error-handling.md` | Fail-open, information disclosure | | `supply-chain.md` | Dependencies, build security | | `logging.md` | Audit failures, log injection | ### Language Guides (`languages/`) - `python.md` - Django, Flask, FastAPI patterns - `javascript.md` - Node, Express, React, Vue, Next.js - `go.md` - Go-specific security patterns - `rust.md` - Rust unsafe blocks, FFI security - `java.md` - Spring, Java EE patterns ### Infrastructure (`infrastructure/`) - `docker.md` - Container security - `kubernetes.md` - K8s RBAC, secrets, policies - `terraform.md` - IaC security - `ci-cd.md` - Pipeline security - `cloud.md` - AWS/GCP/Azure security
Original skill: getsentry/skills/skills/security-review/SKILL.md
Source: https://github.com/getsentry/skills/blob/d18b7aa8ba878354e5c348310230e652f7690f9c/skills/security-review/SKILL.md
License: Apache-2.0
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to the Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
Copyright 2025 Functional Software, Inc. dba Sentry
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
SKILL.md 본문입니다. 원문에서 참조하는 스크립트·보조 파일은 원본 패키지에 포함되어 있습니다.