offsec-web-300

Guides white-box web application security assessment and custom Python exploit development for OSWE certification.

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/yogiex/opencode-cyber-security-skills --skill offsec-web-300-yogiex
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: offsec-web-300
Source: https://github.com/yogiex/opencode-cyber-security-skills/tree/main/skills/offsec-web-300
Command: npx skills add https://github.com/yogiex/opencode-cyber-security-skills --skill offsec-web-300-yogiex

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Preparing for the OffSec WEB-300/OSWE exam requires mastering source code review across five languages and writing fully automated Python exploits, but the material is scattered across dozens of vulnerability classes and case studies. This Skill consolidates the methodology, vulnerable code patterns, exploit templates, and exam strategy into one structured reference. ## Core Features & Use Cases - Source Code Review Methodology: Provides language-specific vulnerable sink patterns for Java, C#, PHP, Python, and JavaScript, plus a data-flow tracing workflow from entry point to sink. - Vulnerability Deep-Dive References: Covers .NET deserialization with ysoserial.net gadget chains, PHP type juggling and magic hashes, blind SQLi, SSTI across template engines, SSRF bypass techniques, blind XXE, and prototype pollution to RCE. - Exploit Development & Exam Strategy: Includes a Python exploit template meeting OSWE requirements (fully automated, no hardcoded sessions), a 47h45m time management plan, and a report template with submission checklist. - Use Case: While reviewing a Java application during exam practice, load the injection-attacks reference to identify a PostgreSQL COPY FROM PROGRAM RCE path, then adapt the Python exploit template to automate the full chain from login to Proof.txt. ## Quick Start Ask the agent to review the target application's source code for exploitable vulnerability patterns and draft a fully automated Python exploit script.

Frequently Asked Questions about offsec-web-300

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a fully automated Python exploit for the OSWE exam?▼

Use the provided exploit template built on the requests library with a session object that performs its own login. The script must run with one command, contain no input() prompts, no hardcoded sessions, and demonstrate the full chain from initial access to retrieving Local.txt and Proof.txt.

How do I find .NET deserialization vulnerabilities in source code?▼

Search the codebase for sinks like BinaryFormatter.Deserialize(), LosFormatter.Deserialize(), or Newtonsoft.Json with TypeNameHandling enabled. Then generate a payload with ysoserial.net using a gadget chain such as TypeConfuseDelegate matched to the target's serializer and .NET version.

What tools are allowed in the OSWE exam?▼

Burp Suite Community, dnSpy, JD-GUI, Visual Studio, and Python are permitted. SQLmap, Burp Suite Pro automation, source code analyzers, and AI tools are explicitly forbidden, so all SQL injection must be performed manually.

How does PHP type juggling bypass authentication?▼

Loose comparison operators like == coerce types, so magic hashes starting with 0e evaluate as float zero and match each other. Passing an array to strcmp() returns null, which loosely equals zero, granting access when the code checks strcmp($_POST['password'], $hash) == 0.

Why does my ysoserial.net payload fail against the target?▼

Gadget chains are .NET framework version dependent, so verify the target's .NET version before generating the payload. Also confirm you selected the correct formatter (LosFormatter vs BinaryFormatter) and check whether the serialized data is encrypted with a key you must extract from the source first.

What is the passing score and structure of the OSWE exam?▼

The exam lasts 47 hours 45 minutes with three machines worth 20, 35, and 45 points, requiring 85 out of 100 to pass. A professional report must be submitted within 24 hours after the exam ends, and privilege escalation is always required since Proof.txt sits at a higher privilege level than Local.txt.