People often ask me "How did you learn how to hack?" The answer: by reading. This page is a collection of the blog posts and other articles that I have accumulated over the years of my journey. Enjoy!
The first point is really interesting! People on bug bounty programs tend to look for the same bugs. So, this guy recommends looking for functionality not usually visible to the user.
Normally, the service comes from the payment provider and the server. However, this person stumbled upon the internal API docs for Stripe.
This API was not locked down because users did not usually visit it.
By using this API, it was possible to forge a payment request.
Payment related webhooks are commonly used in subscription based programs. So, this could be a jackpot!
Character sets are an interesting thing! The history from ASCII to Unicode has a very odd history.
Krebs is talking about domains have similar looking characters.
Someone could buy "amazon.com" but with the letter being a different character than the normal ASCII a. Instead, using a similar looking unicode character.
Gaining Domain Admin from Outside Active Directory- 29
Just a story about an internal pentest. A super fun read! The highlights will be listed below:
Test the easy stuff! Even when you do not think it is going to work, it's a free pass :)
The cracked password was Winter2018!. Remember to look at the password rules for a given company. This will give you an idea on what the password may be. In particular, if it is a quarterly password change, people may use the season + year of the password.
In this, the author chooses a piece of malware to describe the encryption breaking. First, we need to find a mistake. But, what does a mistake look like? Anything from weak encryption algorithms, poor key generators or server-side vulnerabilities.
The first step is identifying where the encryption is being done at. Note: There could be multiple encryption algorithms within a single binary.
A common issue is with random number generators. Some generators are indistinguishable from random noise, while others can be reversed with some effort. If the random number generator was deterministic with time, then it may be possible to figure out the seed used, which could get the key.
Weak encryption algorithms. This goes from a custom cipher that you would likely see in a CTF challenge to something like DES