title: “Offensive Security Certified Expert Exam Report”
author: [“student@youremailaddress.com“, “OSID: XXXX”]
date: “2020-07-25”
subject: “Markdown”
keywords: [Markdown, Example]
subtitle: “OSCE Exam Report”
lang: “en”
titlepage: true
titlepage-color: “483D8B”
titlepage-text-color: “FFFAFA”
titlepage-rule-color: “FFFAFA”
titlepage-rule-height: 2
book: true
classoption: oneside
code-block-font-size: \scriptsize

Intro

The Offensive Security OSCE exam documentation contains all efforts that were conducted in order to pass the Offensive Security Certified Expert exam. This report will be graded from a standpoint of correctness and fullness to all aspects of the exam. The purpose of this report is to ensure that the student has the technical knowledge required to pass the qualifications for the Offensive Security Certified Expert certification.
The student will be required to fill out this exam documentation fully and to include the following sections:

• Methodology walkthrough and detailed outline of steps taken
• Each finding with included screenshots, walkthrough, sample code, and proof.txt if applicable.
• Any additional items that were not included

192.168.XX.200

Proof.txt

Provide the contents of proof.txt.

Vulnerable Command

Provide the command that was found to be exploitable.

Vulnerability Identification

Provide the method and code used to find the vulnerability.

PoC Code

Provide the final proof of concept code used to gain access to the server.

Steps

Provide a detailed account of your methodology in creating the exploit. The steps taken should be able to be easily followed and reproducible if necessary.

192.168.XX.220

Proof.txt

Provide the contents of proof.txt.

Vulnerable Command

Provide the command that was found to be exploitable.

Privilege Escalation

Provide the privilege escalation that was used to gain root on the server.

PoC Code

Provide the final proof of concept code used to gain access to the server.

Screenshots

Provide a screenshot of the id command and the contents of proof.txt.

Steps

Provide a detailed account of your methodology in creating the exploit. The steps taken should be able to be easily followed and reproducible if necessary.

192.168.XX.201

Screenshot

Screenshot requirements are detailed in the control panel.

Steps

Provide a detailed account of your methodology. The steps taken should be able to be easily followed and reproducible if necessary.

192.168.XX.240

PoC Code

Provide the final proof of concept code used to gain access to the server.

Screenshot

Screenshot requirements are detailed in the control panel.

Steps

Provide a detailed account of your methodology in creating the exploit. The steps taken should be able to be easily followed and reproducible if necessary.

Additional Items Not Mentioned in the Report

This section is placed for any additional items that were not mentioned in the overall report.