| Section | Required Content | |--------|------------------| | | Brief summary of the test, targets, and overall outcome (e.g., “Achieved root/administrative access on both machines”) | | Methodology | High-level approach – source code review, attack surface mapping, vulnerability discovery, exploit development | | Vulnerabilities & Exploits | One detailed section per unique vulnerability chain. Include: - Vulnerability type (e.g., SSTI, SQLi, deserialization) - Affected code snippet (with line numbers) - Proof of concept (PoC) – working exploit script - Step-by-step reproduction | | Flags / Proofs | Screenshots of proof.txt (or equivalent) and sensitive data (e.g., /etc/shadow , database contents) | | Remediation | Brief fix for each vulnerability (optional for passing, but good practice) | | Appendix | Full exploit code, curl commands, logs, or additional notes |
Explain why the code is vulnerable and how your input manipulates it. oswe exam report
[Screenshot of exploit output showing local.txt hash: "OSWE8a3f..."] during the exam; however, points can be deducted
Unlike the OSCP (where each flag is independent), the OSWE often requires a chain of exploits to achieve RCE. You are typically given an additional 24 hours
during the exam; however, points can be deducted or nullified for insufficient documentation. Documentation Style:
. Even if you score the required 85 points during the lab time, a poorly documented report can lead to a failure. You are typically given an additional 24 hours after the exam ends to finalize and upload this documentation. Conclusion