In this video we figure out how to do a popunder in Chrome version 59, by using a trick.
We learn how smart contracts written in solidity are deployed, and how it can be used to backdoor a contract.
I wanted to compile a custom Chromium 68 build to totally ignore the obfuscated JavaScript. That was a cool experience, but in the end not necessary - the pop-under trick was super simple and works on Mac, Windows and Linux.
I thought I know Ethereum smart contract security, but this challenge punched me in the face. This video goes over a basic first code review to understand the contract setup.
Exploiting a gitlab 1day. Two CVEs are combined to achieve full remote code execution.
Setting up GitLab in Docker to exploit a gitlab 1day. Two CVEs are combined to achieve full remote code execution.
In this video we identify a backdoor and find the gadgets to do Jump-oriented Programming in a ethereum smart contract.
At first I was not able to solve the mindreader challenge, even though it was supposed to be easy. I have a critical look at my approach and figured out two major mistakes I made.
An actual XSS on google.com by Masato Kinugawa. It abuses a parser differential between a JavaScript enabled and disabled context.
Leaking data through a search cross origin, by abusing a behaviour of Chrome regarding iframed pages that trigger errors.
There are a lot of charlatans out their overhyping by posting misleading content. It's infuriating because a lot of the actual research is less flashy and thus more hidden. Maybe I'm a bit too pessimistic in this video, but I think it's a concrete example we can use talk about it.
At the start we quickly reverse engineer a Java program, but then we move to the main topic - reverse engineer a basic windows .exe to find out how to win the game
This challenge was part of the FLARE-On 2018 CTF. In this video we reverse engineer a basic windows .exe to find out how to win the game. At first we tried to attack the weak crypto but failed. At the end it turns out I had a bug in my code :(