Performing Content Security Policy Bypass
Overview
Cybersecurity skill for performing content security policy bypass. Follows industry best practices and security standards.
When to Use
Trigger phrases:
"performing content security policy bypass"
"Analyze and bypass Content Security Policy implementations to achieve cross-site"
When XSS is found but execution is blocked by Content Security Policy
During web application security assessments to evaluate CSP effectiveness
When testing the robustness of CSP against known bypass techniques
During bug bounty hunting where CSP prevents direct XSS exploitation
When auditing CSP header configuration for security weaknesses
When NOT to Use
- When you lack proper authorization for testing
- For production systems without change management
- When the task requires legal or compliance expertise beyond technical scope
Prerequisites
- Burp Suite for intercepting responses and analyzing CSP headers
- CSP Evaluator (Google) for automated policy analysis
- Understanding of CSP directives (script-src, default-src, style-src, etc.)
- Knowledge of CSP bypass techniques (JSONP, base-uri, object-src)
- Browser developer tools for CSP violation monitoring
- Collection of whitelisted domain JSONP endpoints
Workflow
# Example: IOC detection
import re
IOC_PATTERNS = {
"ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",
"domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",
"hash_md5": r"\b[a-f0-9]{32}\b",
"hash_sha256": r"\b[a-f0-9]{64}\b",
}
def extract_iocs(text: str) -> dict:
return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}
- Plan Operations — Define objectives, scope, and success criteria for content security policy bypass operations.
- Prepare Environment — Set up tools, access, and data sources required for content security policy bypass.
- Execute Core Workflow — Perform the content security policy bypass operations following established procedures.
- Validate Results — Verify that results meet quality standards and objectives.
- Report Findings — Document results, observations, and recommendations.
- Follow Up — Track remediation actions and verify fixes where applicable.
Tools
- Analysis Platform — Data processing and visualization
- Collaboration Tools — Team coordination and knowledge sharing
Process
- Reconnaissance — Gather target information, identify attack surface, enumerate services
- Analysis/Exploitation — Execute the technique, analyze results, document findings
- Reporting — Document IOCs, write findings, provide remediation recommendations
Verification
Anti-Rationalization Table
| Rationalization |
Reality |
| "We are too small to be targeted" |
Automated attacks target everyone. Size does not matter. |
| "Security slows us down" |
A breach slows you down 100x more. Build security in from the start. |
| "We will fix it after launch" |
Vulnerabilities in production are exploited within hours. Fix before deploy. |
1---2name: performing-content-security-policy-bypass3description: Use when analyze and bypass Content Security Policy implementations to achieve cross-site scripting by exploiting misconfigurations, JSONP endpoints, unsafe directives, and policy injection techniques. Use when analyzeing and bypass content security policy implementations to achieve cross-site.4license: Apache-2.05---67# Performing Content Security Policy Bypass89## Overview1011Cybersecurity skill for performing content security policy bypass. Follows industry best practices and security standards.1213## When to Use14**Trigger phrases:**15- "performing content security policy bypass"16- "Analyze and bypass Content Security Policy implementations to achieve cross-site"1718- When XSS is found but execution is blocked by Content Security Policy19- During web application security assessments to evaluate CSP effectiveness20- When testing the robustness of CSP against known bypass techniques21- During bug bounty hunting where CSP prevents direct XSS exploitation22- When auditing CSP header configuration for security weaknesses232425## When NOT to Use2627- When you lack proper authorization for testing28- For production systems without change management29- When the task requires legal or compliance expertise beyond technical scope303132## Prerequisites33- Burp Suite for intercepting responses and analyzing CSP headers34- CSP Evaluator (Google) for automated policy analysis35- Understanding of CSP directives (script-src, default-src, style-src, etc.)36- Knowledge of CSP bypass techniques (JSONP, base-uri, object-src)37- Browser developer tools for CSP violation monitoring38- Collection of whitelisted domain JSONP endpoints3940## Workflow4142```python43# Example: IOC detection44import re4546IOC_PATTERNS = {47 "ip": r"\b(?:\d{1,3}\.){3}\d{1,3}\b",48 "domain": r"\b[a-z0-9-]+\.[a-z]{2,}\b",49 "hash_md5": r"\b[a-f0-9]{32}\b",50 "hash_sha256": r"\b[a-f0-9]{64}\b",51}5253def extract_iocs(text: str) -> dict:54 return {k: re.findall(v, text) for k, v in IOC_PATTERNS.items()}55```56571. **Plan Operations** — Define objectives, scope, and success criteria for content security policy bypass operations.582. **Prepare Environment** — Set up tools, access, and data sources required for content security policy bypass.593. **Execute Core Workflow** — Perform the content security policy bypass operations following established procedures.604. **Validate Results** — Verify that results meet quality standards and objectives.615. **Report Findings** — Document results, observations, and recommendations.626. **Follow Up** — Track remediation actions and verify fixes where applicable.6364## Tools6566- **Analysis Platform** — Data processing and visualization67- **Collaboration Tools** — Team coordination and knowledge sharing686970## Process71721. **Reconnaissance** — Gather target information, identify attack surface, enumerate services731. **Analysis/Exploitation** — Execute the technique, analyze results, document findings741. **Reporting** — Document IOCs, write findings, provide remediation recommendations7576## Verification7778- [ ] All content security policy bypass procedures executed completely and documented79- [ ] Findings validated against multiple data sources80- [ ] False positives identified and filtered81- [ ] Results documented with evidence and timestamps82- [ ] Recommendations provided with risk-based prioritization8384## Anti-Rationalization Table8586| Rationalization | Reality |87|---|---|88| "We are too small to be targeted" | Automated attacks target everyone. Size does not matter. |89| "Security slows us down" | A breach slows you down 100x more. Build security in from the start. |90| "We will fix it after launch" | Vulnerabilities in production are exploited within hours. Fix before deploy. |