DVWA VS CyberChef

There's also a bunch of intentionally vulnerable Webapps and VMs aimed at demonstrating potential footholds and common exploits leading to owning of the host including but not limited to: bWAPP, Damn Vulnerable Web App, WebGoat, Metasploitable 3, Mutillidae, Juice Shop

I'd suggest you to download for example a VM of Damn Vulnerable Web Application (https://github.com/digininja/DVWA), learn and practice the attacks, and then try to protect the host from these attacks to prevent or limit access to the system.

I deployed a Damn Vulnerable Web Application (DVWA) for you, I DM'ed the url and creds. It's a controlled sandbox, intentionally vulnerable app for you to try out your hackerman skills. Go nuts, have fun dude.

For app security check out the damn vulnerable web app: https://github.com/digininja/DVWA

A fresh install laptop is probably going to be a frustrating first place to start as it is unlikely to be exposing any services for you to scan or test. You could install some vulnerable services, like the damn vulnerable web application here which has good setup instructions and many, many walkthroughs.

You could spin up a version of dvwa and scan that. https://github.com/digininja/DVWA

sudo git clone https://github.com/digininja/DVWA/git

DVWA is a pretty solid educational, training application that is meant for this purpose. There are a bunch of different modules, but one is bruteforcing passwords.

Damn Vulnerable Web App

Then we take the encrypted text and use CyberChef to decrypt it.

Let's go to CyberChef and insert our pieces of evidence.

A parameter was changed from '2AMBCgIQBg' to 'CgIIAdgDAQ%3D%3D' which is just the correct base64 encoding they should have been using the entire time.

I don't think this was a hostile action by Google, I think someone just added better input validation for security reasons and it accidently broke the bad requests they were sending.

https://gchq.github.io/CyberChef/#recipe=URL_Decode()From_Ba...

❗This is indeed the flag, but the text is encrypted with Base64. Usually, the presence of padding character "=" indicates that's Base64 type of encoding (but that's only one of the hints). To decrypt it, we can use CyberChef. Copy-paste the text and we either:

It uses a combination of magic bytes (like the `file` command), entropy analysis and character frequency detection to determine whether an output is likely to be of interest to the user.

The file type mechanism is written here[0]. There's a list of all signatures we detect here[1].

[0] https://github.com/gchq/CyberChef/blob/master/src/core/lib/F...

I think this can be deciphered using CyberChef...