🌟
Noel's Cyberkshetra Blogspace
LinkedIn ProfileGithub ProfilePersonal Blogspot
  • Welcome to my Gitbooks Page
  • 💽Let's Defend Blue Team Walkthroughs
    • SOC164 - Suspicious Mshta Behavior Alert
    • SOC147 - SSH Scan Activity Alert
    • SOC146  -  Phishing Mail Detected Alert
    • SOC145 - Ransomware Detected Alert
    • SOC144  -  New scheduled task created Alert
    • SOC143 - Password Stealer Detected Alert
    • SOC141  -  Phishing URL Detected Alert
    • SOC141 - Phishing URL Detected Alert
    • SOC137 — Malicious File/Script Download Attempt: A Walkthrough
    • SOC109  -  Emotet Malware Detected Alert
    • SOC104 - Malware Detected Alert
    • SOC101  -  Phishing Mail Detected Alert
    • HTTP Basic Auth: Let's Defend DFIR Challenge
    • ShellShock Attack: Let’s Defend Challenge
    • 2021’s 0-Day MSHTML: Let's Defend Lab
  • 🤺BTLO Walkthroughs
    • BTLO: Network Analysis-Web Shell Challenge
    • BTLO: Suspicious USB Stick Challenge
  • 💒WiCYS CyberStart
    • Chapter 1 - Amsterdam A Running Start
      • WiCYS CyberStart (Amsterdam) Challenge 1
      • WiCYS CyberStart (Amsterdam) Challenge 2
      • WiCYS CyberStart (Amsterdam) Challenge 3
      • WiCYS CyberStart (Amsterdam) Challenge 4
    • Chapter 2 - Tokyo Patterns of Behaviour
      • WiCYS CyberStart (Tokyo) Challenge 1
      • WiCYS CyberStart (Tokyo) Challenge 2
      • WiCYS CyberStart (Tokyo) Challenge 3
      • WiCYS CyberStart (Tokyo) Challenge 4
    • Chapter 3 - Barcelona In the thick of it
      • WiCYS CyberStart (Barcelona) Challenge 1
      • WiCYS CyberStart (Barcelona) Challenge 2
      • WiCYS Cyberstart (Barcelona) Challenge 3
      • WiCYS CyberStart (Barcelona) Challenge 4
  • 📕Technical Cyber articles
    • An in-depth analysis of an Intrusion Prevention System
    • DevSecOps-Making a difference from traditional DevOps
    • CVE - 2020–1472 (Zerologon Vulnerability)-Exploitation & Remediation
    • Computer Forensics Acquisition
    • Cyber Hygiene Tips
    • Hack your System - Linux Edition
    • Markovian Parallax Denigrate-Breaking the cipher
    • SIEM-Incorporating Incident Response into Network Security
    • Social Engineering-A leading cause for vulnerability occurrence
    • Report Writing in Digital & Multimedia Forensics
    • Zero-Day Vulnerabilities: A short overview
    • Zero Trust Network Access-A solution to Network Security
  • 🧑‍💻Hack The Box : Starting Point Machines
    • Meow
    • Fawn
    • Dancing
    • Redeemer
Powered by GitBook
On this page
  • Briefing L02 C04
  • Start-Up Troubles
  • Approach 1 — Editing the HTML code
  • Approach 2 — SQL Injection
  • Approach 3 — Using the web console
  • Flag Capture
  • Scoreboard
  1. WiCYS CyberStart
  2. Chapter 2 - Tokyo Patterns of Behaviour

WiCYS CyberStart (Tokyo) Challenge 4

Web Login vulnerability

PreviousWiCYS CyberStart (Tokyo) Challenge 3NextChapter 3 - Barcelona In the thick of it

Last updated 3 years ago

Briefing L02 C04

Start-Up Troubles

A successful new start-up that sells electric scooters has discovered a handful of their customers’ accounts have been hacked! And guess who we believe might be behind it? Yep, you’ve guessed it, the Yakoottees. Having only just entered the market and keen to maintain their otherwise excellent reputation, this business needs our help to run a security audit of their login system. Can you spot any security holes?

Tip: Successfully login to get the flag.

We come across this login page, belonging to the Zip Zap Rides startup

The manual says that there is a vulnerability on this website. Let’s hunt that down!

I took three approaches to solve this, each more complex than the next one.

Approach 1 — Editing the HTML code

If you look closely, there are 4 parameters whose values we need to know. These are email, password, submittedEmail, and SubmittedPassword

Since the values were not present, I tried to manipulate the source code, inserting custom values

This did not work, as I was repeatedly changing comments one after the other, to get the login page to work

Approach 2 — SQL Injection

That approach did not work as well

Approach 3 — Using the web console

Right. This was the way out.

Since the console had come in handy in the previous challenge, let’s make use of it.

Right click ->Console

We can observe that the parameters for login were ‘email’ and ‘password’.Let’s try querying it against the console

This is what we get:-

We get what we have been looking for!

Login page credentials

Email — bonita@zip-zap-rides.com

Password — letmein

Flag Capture

Use it to log in and we get the flag

Flag — pgHGwHToGfFE2MC4BF1A

Scoreboard

It’s time to bid farewell to the Tokyo base (especially when it gave us our hardest challenge yet) and set base somewhere else. Let’s see where our CyberStart journey takes us.

Onward to the next challenge!

Having no email address (from the company) to use in the email field, it was worth a try to try payloads from this and spray it on the password section

💒
Github repository