🎯 What You'll Learn
- Trace tainted input through application code
- Exploit injection inside ORM and prepared-statement misuse
- Abuse PostgreSQL features for read/write and RCE
- Reason about second-order injection
Overview
Real applications hide injection behind ORMs, stored procedures and strict typing. This lab takes a white-box approach to find and exploit subtle injection in a Java/Spring + PostgreSQL stack.
Core Topics
- White-box source review
- PostgreSQL internals for attackers
- Second-order injection
- Stacked queries
Prerequisites
A working KaliRange lab environment and comfort with the Linux command line.
Recommended Workflow
- Spin up the target in your KaliRange lab environment and confirm connectivity.
- Enumerate the target thoroughly before touching any exploit — information first.
- Reproduce each technique by hand so you understand why it works, not just the command.
- Capture evidence (commands, output, screenshots) as you go.
- Write a short note on how a defender would detect or prevent what you just did.
Only ever run these techniques against systems you own or have explicit written permission to test. Practise inside your own KaliRange lab.
Your Goal
Work through every task in your own lab, document your findings as you would on a real engagement, then note the defensive takeaways.
Ready to practise. Work through the steps above at your own pace, then move on to a related lab.