Repository: BehiSecc/VibeSec-Skill Branch: main Commit: 0590993b35ad Files: 3 Total size: 39.4 KB Directory structure: gitextract_7ord5vbe/ ├── LICENSE ├── README.md └── SKILL.md ================================================ FILE CONTENTS ================================================ ================================================ FILE: LICENSE ================================================ 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 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 APPENDIX: How to apply the Apache License to your work. To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives. Copyright [yyyy] [name of copyright owner] 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. ================================================ FILE: README.md ================================================ # VibeSec-Skill > **Stop vibe coding vulnerabilities into production.** An AI skill that brings 5+ years of bug bounty hunting experience directly into your AI coding workflow - so LLM models write secure code from the start. ## Introduction Vibe coding is fun until your app ends up on social media for all the wrong reasons. We have all seen the posts/memes: * API keys hardcoded in JavaScript bundles * IDOR vulnerabilities allowing user data dumps * No authentication for sensitive pages * Weak passwords for admin panels Security gaps aren't obvious until someone exploits them. Without the right guidance, AI will confidently ship vulnerable patterns alongside your features. VibeSec is an AI Skill that acts as a security-first co-pilot. It teaches your selected model to approach your code from a bug hunter's perspective, catching vulnerabilities before they ship. ## 📚 Table of Contents - [VibeSec-Skill](#VibeSec-Skill) - [📥 Installation](#-installation) - [🛡️ Covered Vulnerabilities](#️-covered-vulnerabilities) - [🚀 Quick Start](#-quick-start) - [🤝 Contribution](#-contribution) - [📬 Contact](#-contact) >[!Tip] >This skill already covers 60-70% of the common vulnerabilities. However, if you need a more robust version with more vulnerability coverage, please visit [vibesec.sh](https://vibesec.sh/) ## 📥 Installation -
Claude Code * Clone this repository: `git clone https://github.com/BehiSecc/VibeSec-Skill` * Add it to `~/.claude/skills` (global) or `.claude/skills` in your project directory (project-only).
-
Cursor * Clone this repository: `git clone https://github.com/BehiSecc/VibeSec-Skill` * Add it to `~/.cursor/skills` (global) or `.cursor/skills` in your project directory (project-only).
-
Codex * Clone this repository: `git clone https://github.com/BehiSecc/VibeSec-Skill` * Add it to `~/.agents/skills` (global) or `.agents/skills` in your project directory (project-only).
-
Github Copilot * Clone this repository: `git clone https://github.com/BehiSecc/VibeSec-Skill` * Add it to `~/.copilot/skills` (global) or `.github/skills` in your project directory (project-only).
-
Antigravity * Clone this repository: `git clone https://github.com/BehiSecc/VibeSec-Skill` * Add it to `~/.gemini/antigravity/skills/` (global) or `.agent/skills/` in your project directory (project-only).
## 🛡️ Covered Vulnerabilities VibeSec provides comprehensive protection against: | Category | Covered Vulnerabilities | |----------|-----------------| | **Access Control** | IDOR, Privilege Escalation, Horizontal/Vertical Access, Mass Assignment, Token Revocation | | **Client-Side** | XSS (Stored, Reflected, DOM), CSRF, Secret Key Exposure, Open Redirect | | **Server-Side** | SSRF, SQL Injection, XXE, Path Traversal, Insecure File Upload | | **Authentication** | Weak Passwords, Session Management, Account Lifecycle, JWT Security | | **API Security** | Mass Assignment, GraphQL Security | ### Deep Coverage Includes: - ✅ **Bypass techniques** - Not just "sanitize input" but specific bypasses attackers use - ✅ **Edge cases** - URL fragments, DNS rebinding, polyglot files, Unicode tricks - ✅ **Framework-aware** - Patterns for React, Vue, Node.js, Python, Java, .NET - ✅ **Cloud-aware** - Metadata endpoint protection for AWS, GCP, Azure - ✅ **Checklists** - Actionable verification steps for each vulnerability class ## 🚀 Quick Start ```markdown # Add the skill to your project dir: "I'm building a [web app description]. Please follow secure coding practices." # Claude/Codex/etc will now automatically: # - Implement proper access controls # - Add security headers # - Validate and sanitize all inputs # - Flag potential security issues ``` ## 🤝 Contribution If you have suggestions, improvements, or new resources to add: 1. Fork this repo 2. Make your changes 3. Submit a Pull Request You can also open an **Issue** 🐛 if you spot something that needs fixing. ## 📬 Contact If you want to contact me, you can reach me on [X](https://x.com/Behi_Sec). ================================================ FILE: SKILL.md ================================================ --- name: VibeSec-Skill description: This skill helps Claude write secure web applications. Use this when working on any web application or when a user requests a scan or audit to ensure security best practices are followed. --- # Secure Coding Guide for Web Applications ## Overview This guide provides comprehensive secure coding practices for web applications. As an AI assistant, your role is to approach code from a **bug hunter's perspective** and make applications **as secure as possible** without breaking functionality. **Key Principles:** - Defense in depth: Never rely on a single security control - Fail securely: When something fails, fail closed (deny access) - Least privilege: Grant minimum permissions necessary - Input validation: Never trust user input, validate everything server-side - Output encoding: Encode data appropriately for the context it's rendered in --- ## Access Control Issues Access control vulnerabilities occur when users can access resources or perform actions beyond their intended permissions. ### Core Requirements For **every data point and action** that requires authentication: 1. **User-Level Authorization** - Each user must only access/modify their own data - No user should access data from other users or organizations - Always verify ownership at the data layer, not just the route level 2. **Use UUIDs Instead of Sequential IDs** - Use UUIDv4 or similar non-guessable identifiers - Exception: Only use sequential IDs if explicitly requested by user 3. **Account Lifecycle Handling** - When a user is removed from an organization: immediately revoke all access tokens and sessions - When an account is deleted/deactivated: invalidate all active sessions and API keys - Implement token revocation lists or short-lived tokens with refresh mechanisms ### Authorization Checks Checklist - [ ] Verify user owns the resource on every request (don't trust client-side data) - [ ] Check organization membership for multi-tenant apps - [ ] Validate role permissions for role-based actions - [ ] Re-validate permissions after any privilege change - [ ] Check parent resource ownership (e.g., if accessing a comment, verify user owns the parent post) ### Common Pitfalls to Avoid - **IDOR (Insecure Direct Object Reference)**: Always verify the requesting user has permission to access the requested resource ID - **Privilege Escalation**: Validate role changes server-side; never trust role info from client - **Horizontal Access**: User A accessing User B's resources with the same privilege level - **Vertical Access**: Regular user accessing admin functionality - **Mass Assignment**: Filter which fields users can update; don't blindly accept all request body fields ### Implementation Pattern ``` # Pseudocode for secure resource access function getResource(resourceId, currentUser): resource = database.find(resourceId) if resource is null: return 404 # Don't reveal if resource exists if resource.ownerId != currentUser.id: if not currentUser.hasOrgAccess(resource.orgId): return 404 # Return 404, not 403, to prevent enumeration return resource ``` --- ## Client-Side Bugs ### Cross-Site Scripting (XSS) Every input controllable by the user—whether directly or indirectly—must be sanitized against XSS. #### Input Sources to Protect **Direct Inputs:** - Form fields (email, name, bio, comments, etc.) - Search queries - File names during upload - Rich text editors / WYSIWYG content **Indirect Inputs:** - URL parameters and query strings - URL fragments (hash values) - HTTP headers used in the application (Referer, User-Agent if displayed) - Data from third-party APIs displayed to users - WebSocket messages - postMessage data from iframes - LocalStorage/SessionStorage values if rendered **Often Overlooked:** - Error messages that reflect user input - PDF/document generators that accept HTML - Email templates with user data - Log viewers in admin panels - JSON responses rendered as HTML - SVG file uploads (can contain JavaScript) - Markdown rendering (if allowing HTML) #### Protection Strategies 1. **Output Encoding** (Context-Specific) - HTML context: HTML entity encode (`<` → `<`) - JavaScript context: JavaScript escape - URL context: URL encode - CSS context: CSS escape - Use framework's built-in escaping (React's JSX, Vue's {{ }}, etc.) 2. **Content Security Policy (CSP)** ``` Content-Security-Policy: default-src 'self'; script-src 'self'; style-src 'self' 'unsafe-inline'; img-src 'self' data: https:; font-src 'self'; connect-src 'self' https://api.yourdomain.com; frame-ancestors 'none'; base-uri 'self'; form-action 'self'; ``` - Avoid `'unsafe-inline'` and `'unsafe-eval'` for scripts - Use nonces or hashes for inline scripts when necessary - Report violations: `report-uri /csp-report` 3. **Input Sanitization** - Use established libraries (DOMPurify for HTML) - Whitelist allowed tags/attributes for rich text - Strip or encode dangerous patterns 4. **Additional Headers** - `X-Content-Type-Options: nosniff` - `X-Frame-Options: DENY` (or use CSP frame-ancestors) --- ### Cross-Site Request Forgery (CSRF) Every state-changing endpoint must be protected against CSRF attacks. #### Endpoints Requiring CSRF Protection **Authenticated Actions:** - All POST, PUT, PATCH, DELETE requests - Any GET request that changes state (fix these to use proper HTTP methods) - File uploads - Settings changes - Payment/transaction endpoints **Pre-Authentication Actions:** - Login endpoints (prevent login CSRF) - Signup endpoints - Password reset request endpoints - Password change endpoints - Email/phone verification endpoints - OAuth callback endpoints #### Protection Mechanisms 1. **CSRF Tokens** - Generate cryptographically random tokens - Tie token to user session - Validate on every state-changing request - Regenerate after login (prevent session fixation combo) 2. **SameSite Cookies** ``` Set-Cookie: session=abc123; SameSite=Strict; Secure; HttpOnly ``` - `Strict`: Cookie never sent cross-site (best security) - `Lax`: Cookie sent on top-level navigations (good balance) - Always combine with CSRF tokens for defense in depth 3. **Double Submit Cookie Pattern** - Send CSRF token in both cookie and request body/header - Server validates they match #### Edge Cases and Common Mistakes - **Token presence check**: CSRF validation must NOT depend on whether the token is present, always require it - **Token per form**: Consider unique tokens per form for sensitive operations - **JSON APIs**: Don't assume JSON content-type prevents CSRF; validate Origin/Referer headers AND use tokens - **CORS misconfiguration**: Overly permissive CORS can bypass SameSite cookies - **Subdomains**: CSRF tokens should be scoped because subdomain takeover can lead to CSRF - **Flash/PDF uploads**: Legacy browser plugins could bypass SameSite - **GET requests with side effects**: Never perform state changes on GET - **Token leakage**: Don't include CSRF tokens in URLs - **Token in URL vs Header**: Prefer custom headers (X-CSRF-Token) over URL parameters #### Verification Checklist - [ ] Token is cryptographically random (use secure random generator) - [ ] Token is tied to user session - [ ] Token is validated server-side on all state-changing requests - [ ] Missing token = rejected request - [ ] Token regenerated on authentication state change - [ ] SameSite cookie attribute is set - [ ] Secure and HttpOnly flags on session cookies --- ### Secret Keys and Sensitive Data Exposure No secrets or sensitive information should be accessible to client-side code. #### Never Expose in Client-Side Code **API Keys and Secrets:** - Third-party API keys (Stripe, AWS, etc.) - Database connection strings - JWT signing secrets - Encryption keys - OAuth client secrets - Internal service URLs/credentials **Sensitive User Data:** - Full credit card numbers - Social Security Numbers - Passwords (even hashed) - Security questions/answers - Full phone numbers (mask them: ***-***-1234) - Sensitive PII that isn't needed for display **Infrastructure Details:** - Internal IP addresses - Database schemas - Debug information - Stack traces in production - Server software versions #### Where Secrets Hide (Check These!) - JavaScript bundles (including source maps) - HTML comments - Hidden form fields - Data attributes - LocalStorage/SessionStorage - Initial state/hydration data in SSR apps - Environment variables exposed via build tools (NEXT_PUBLIC_*, REACT_APP_*) #### Best Practices 1. **Environment Variables**: Store secrets in `.env` files 2. **Server-Side Only**: Make API calls requiring secrets from backend only --- ## Open Redirect Any endpoint accepting a URL for redirection must be protected against open redirect attacks. ### Protection Strategies 1. **Allowlist Validation** ``` allowed_domains = ['yourdomain.com', 'app.yourdomain.com'] function isValidRedirect(url): parsed = parseUrl(url) return parsed.hostname in allowed_domains ``` 2. **Relative URLs Only** - Only accept paths (e.g., `/dashboard`) not full URLs - Validate the path starts with `/` and doesn't contain `//` 3. **Indirect References** - Use a mapping instead of raw URLs: `?redirect=dashboard` → lookup to `/dashboard` ### Bypass Techniques to Block | Technique | Example | Why It Works | |-----------|---------|--------------| | @ symbol | `https://legit.com@evil.com` | Browser navigates to evil.com with legit.com as username | | Subdomain abuse | `https://legit.com.evil.com` | evil.com owns the subdomain | | Protocol tricks | `javascript:alert(1)` | XSS via redirect | | Double URL encoding | `%252f%252fevil.com` | Decodes to `//evil.com` after double decode | | Backslash | `https://legit.com\@evil.com` | Some parsers normalize `\` to `/` | | Null byte | `https://legit.com%00.evil.com` | Some parsers truncate at null | | Tab/newline | `https://legit.com%09.evil.com` | Whitespace confusion | | Unicode normalization | `https://legіt.com` (Cyrillic і) | IDN homograph attack | | Data URLs | `data:text/html,