OSCP Report Template: Offensive Security Lab/Exam Penetration Test Report
OSCP Report Template: Offensive Security Lab/Exam Penetration Test Report
student@emailaddress.com Student-ID
2020-XX-XX
Contents
1 Offensive Security Exam Penetration Test Report
1.1 Introduction
1.2 Objective
1.3 Requirements
2 High-Level Summary
2.1 Recommendations
3 Methodologies
4 Additional Items
The Offensive Security Exam penetration test report contains all efforts that were conducted in order to
pass the Offensive Security 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 a full understanding of penetration testing
methodologies as well as the technical knowledge to pass the qualifications for the Offensive Security
Certified Professional.
Objective
The objective of this assessment is to perform an internal penetration test against the Offensive
Security Lab/Exam network.
The student is tasked with following methodical approach in obtaining access to the objective goals.
This test should simulate an actual penetration test and how you would start from beginning to end,
including the overall report.
An example page has already been created for you at the latter portions of this document that should
give you ample information on what is expected to pass this course.
Use the sample report as a guideline to get you through the reporting.
Requirements
The student will be required to fill out this penetration testing report fully and to include the following
sections:
Each finding with included screenshots, walkthrough, sample code, and proof.txt if applicable
Any additional items that were not included
High-Level Summary
I was tasked with performing an internal penetration test towards Offensive Security Exam.
An internal penetration test is a dedicated attack against internally connected systems.
The focus of this test is to perform attacks, similar to those of a hacker and attempt to infiltrate
Offensive Security’s internal exam systems – the THINC.local domain.
My overall objective was to evaluate the network, identify systems, and exploit flaws while reporting the
findings back to Offensive Security.
When performing the internal penetration test, there were several alarming vulnerabilities that were
identified on Offensive Security’s network.
When performing the attacks, I was able to gain access to multiple machines, primarily due to outdated
patches and poor security configurations.
During the testing, I had administrative level access to multiple systems.
All systems were successfully exploited and access granted.
These systems as well as a brief description on how access was obtained are listed below:
Recommendations
I recommend patching the vulnerabilities identified during the testing to ensure that an attacker cannot
exploit these systems in the future.
One thing to remember is that these systems require frequent patching and once patched, should
remain on a regular patch program to protect additional vulnerabilities that are discovered at a later
date.
Methodologies
I utilized a widely adopted approach to performing penetration testing that is effective in testing how
well the Offensive Security Exam environments is secured.
Below is a breakout of how I was able to identify and exploit the variety of systems and includes all
individual vulnerabilities found.
Information Gathering
The information gathering portion of a penetration test focuses on identifying the scope of the
penetration test.
During this penetration test, I was tasked with exploiting the exam network.
The specific IP addresses were:
Exam Network
192.168.
192.168.
192.168.
192.168.
192.168.
Penetration
The penetration testing portions of the assessment focus heavily on gaining access to a variety of
systems.
During this penetration test, I was able to successfully gain access to X out of the X systems.
System IP: 192.168.x.x
Service Enumeration
The service enumeration portion of a penetration test focuses on gathering information about what
services are alive on a system or systems.
This is valuable for an attacker as it provides detailed information on potential attack vectors into a
system.
Understanding what applications are running on the system gives an attacker needed information
before performing the actual penetration test.
In some cases, some ports may not be listed.
UDP: 1434,161
Additional info about where the initial shell was acquired from
Vulnerability Explanation:
Vulnerability Fix:
Severity:
Local.txt Contents
Privilege Escalation
Vulnerability Exploited:
Vulnerability Explanation:
Vulnerability Fix:
Severity:
Exploit Code:
Proof.txt Contents:
System IP: 192.168.x.x
Service Enumeration
UDP: 1434,161
Additional info about where the initial shell was acquired from
Vulnerability Explanation:
Vulnerability Fix:
Severity:
Local.txt Contents
Privilege Escalation
Vulnerability Exploited:
Vulnerability Explanation:
Vulnerability Fix:
Severity:
Exploit Code:
Proof.txt Contents:
System IP: 192.168.x.x
Service Enumeration
UDP: 1434,161
Additional info about where the initial shell was acquired from
Vulnerability Explanation:
Vulnerability Fix:
Severity:
Local.txt Contents
Privilege Escalation
Vulnerability Exploited:
Vulnerability Explanation:
Vulnerability Fix:
Severity:
Exploit Code:
Proof.txt Contents:
System IP: 192.168.x.x
Service Enumeration
UDP: 1434,161
Additional info about where the initial shell was acquired from
Vulnerability Explanation:
Vulnerability Fix:
Severity:
Local.txt Contents
Privilege Escalation
Vulnerability Exploited:
Vulnerability Explanation:
Vulnerability Fix:
Severity:
Exploit Code:
Proof.txt Contents:
System IP: 192.168.x.x
**Vulnerability Exploited: **
Proof Screenshot:
Maintaining Access
Maintaining access to a system is important to us as attackers, ensuring that we can get back into a
system after it has been exploited is invaluable.
The maintaining access phase of the penetration test focuses on ensuring that once the focused attack
has occurred (i.e. a buffer overflow), we have administrative access over the system again.
Many exploits may only be exploitable once and we may never be able to get back into a system after
we have already performed the exploit.
House Cleaning
The house cleaning portions of the assessment ensures that remnants of the penetration test are
removed.
Often fragments of tools or user accounts are left on an organization's computer which can cause
security issues down the road.
Ensuring that we are meticulous and no remnants of our penetration test are left over is important.
After collecting trophies from the exam network was completed, Alec removed all user accounts and
passwords as well as the Meterpreter services installed on the system.
Offensive Security should not have to remove any user accounts or services from the system.
Additional Items
For the exam, I used my Metasploit/Meterpreter allowance on the following machine: 192.168.x.x