OSCP – Penetration Testing With Kali – Overview

 

offsec

Intro:

My experience with penetration testing before taking this course was nearly nothing.

Pre-Experience:

1-2 years of system administration

Almost done with a BS in IT Security

Several years of captaining a CCDC team. (Collegiate Cyber Defense Team)

Other than that, I was comfortable with Linux, Server Administration, Python and other sys-adminy type stuffs. I would highly recommend at least getting comfortable with the following concepts before jumping into the labs:

Web Servers,Linux, Windows Servers, DNS, FTP, SMB, SMTP, POP3, SNMP, etc.

You don’t need to know everything about these concepts but you should know enough to explain what they are and how they generally work.

Exercise:

The exercises are pretty well laid out. They advance slowly and near the end of the exercises, you are required to understand earlier exercises. They skim many of the concepts needed to get through the labs and it is up to the student to expound on any given topic. If you already have lots of professional experience, you might not need to go through the exercises but if you are like me, the exercises are definitely necessary.

Labs:

The labs are pretty impressive. Lots of blogs go over the structure of the lab so I will save my characters. However, the range of concepts needed to successfully get access to most of the boxes is very broad. Only a couple boxes have repeat vulnerabilities and these typically have multiple paths to root. The notoriety of gh0st, pain, sufferance and humble is definitely well deserved. I spent lots of time with these and ended up with a low priv shell on pain and nothing on sufferance. I did end up getting root on gh0st and humble though. Had I extended my lab, sufferance would have been on the agenda.

The labs were awesome at making the student build his own toolkit and create his own methodology which is where I think its real value comes in. Figuring out what tools worked best was a huge part of the learning process.

Exam:

The exam was hard. I went in not really knowing what to expect. Even though my toolkit was proven throughout the labs, it seemed as if it wasn’t enough for the exam. I spent 18 hours on the exam and at 3 AM, when my brain wasn’t working quite well, I decided to call it a day.

Fast forward a couple days.. And I got that awesome email..

We are happy to inform you that you have successfully completed the Penetration Testing with Kali Linux certification exam and have obtained your Offensive Security Certified Professional (OSCP) certification.

Recap:

Overall, I would say I learned more from the PWK and OSCP process than I have from any one course in school. Like everyone else who took it, I would highly recommend the course! It is a very rewarding exam, it will be interesting to see how much this stuff pertains to actual penetration testing! I do wish there was more AD stuff but that was about my only thought on improvements!

How the Hacking Team Got Hacked

The Hacking Team is a group of 50+ hackers who provide offensive tools for governments across 6 continents. In mid-2015, they were exposed to the world. Everything from their source code to their email database was published on their defaced Twitter page via a torrent.

Little was known about the attack. Until several days ago. Phineas Fisher posted a full write-up on the steps taken to gain access and ex filtrate the goods.

His write-up can be found here on Ghost Bin.

The tactics used by Fisher are very complicated. It’s easy to say that this guy definitely is not a noob. You can check out the link about for the full write-up which is pretty interesting or if you don’t got time for that, I summarized for you.

For Fisher, Hacking Team was a perfect target. According to him, it was run by a “Fascist” and worked against “journalists, activists, political opposition, and other threats to their power”

Fisher followed the typical steps to gather information for a target. He used Google, Subdomain Enumeration, Whois and Port Scanning. These are your typical beginning steps. After this he began to collect information from social sites such as LinkedIn and Metadata from public files. Once again, these are all typical steps for reconnaissance.

Fisher avoided social engineering, after all, the Hacking Team are experts at it so they likely know how to spot spear phishing!

With all this information collected, Fisher found that they don’t have much exposed to the internet. What they did have was a website, a mail server, a couple routers, two VPN appliances and a spam filter.

His options were pretty slim so he began to search for a 0day in an embedded device. This is that impressive part..

After two weeks of reverse engineering, he had a remote root exploit. And after some more testing and assuring that it would not raise a red flag, he created a back door firmware to hide his 0day.

He did not include his exploit or the device used since he claims that it still is not patched.

Once he was in their network, his process was pretty straight forward. Slow network scans and a NetBios poisoner responder.py

He soon finds their backups and attained access to their email database and eventually their development network. He used iscsi to access their backups and mounted them using some clever iptables rules.

He ended up pulling all their passwords as well which he lists in the report.

HACKINGTEAM         c.pozzi         P4ssword

Using powershell, he downloaded all the mailboxes and then used his proxy and smb to download all the files.

All of the emails leaked can be found here.

He included quite a few links to all the tools he used and some good times and use cases for those. I would recommend you check that out!

It appears that at the end of his summary he encourages similar behavior. Heres an excerpt from his report..

“Hacking guides often end with a disclaimer: this information is for
educational purposes only, be an ethical hacker, don’t attack systems you
don’t have permission to, etc. I’ll say the same, but with a more rebellious
conception of “ethical” hacking. Leaking documents, expropriating money from
banks, and working to secure the computers of ordinary people is ethical
hacking. However, most people who call themselves “ethical hackers” just work
to secure those who pay their high consulting fees, who are often those most
deserving to be hacked.”

 

However, the Hacking Team seems to call Fisher out on some of the details..

Moral of the story, no one is invincible, and there is always someone out there ready to play your game better than you.

hackingteam hacked logo

Credit: Steve Ragan / Twitter

 

 

Cybersecurity Information Sharing Act and your privacy

Since the first computer virus in 1989, the US government has been struggling to keep up with the rapidly evolving world of cybersecurity. Hackers use constantly evolving methods while Congress sluggishly passes inefficient measures against these hackers. Over the past 30 or so years, multiple bills have been put in place to battle this misuse of technology. The most recent bill is the CISA.

The Cybersecurity Information Sharing Act passed in the Senate in Oct. with a whopping vote of 74-21. This bills main purpose is to help prevent data breaches like the famous Office of Personnel Managements breach that exposed the personal data of more than 20 million current and former federal employees.

CISA aims to do this by offering legal protection to companies who opt in, enabling these companies to share information without the risk of legal repercussion. In theory, when a company is attacked, the federal government is alerted immediately and the warning is distributed to all companies taking part in CISA.

Why does this need to go through Congress?

CISA eliminates a company’s liability, thus, protecting them from lawsuits for sharing too much information.

Some privacy advocates however have major concerns regarding CISA. Several senators took heed of these warnings and proposed amendments to the bill, such as requiring companies to remove personal data from any information before sharing. Ultimately, all of the proposed amendments were shut down and the bill was passed without any of the privacy reforms.

Privacy advocates also aren’t sure how much the bill will even promote data sharing to mitigate attacks. This is based on the argument that data sharing is already taking place among many companies and introducing the government has not historically improved matters. Ben Johnson, Chief Security Strategist is quoted saying in a Forbes article:

“While cyber defense, security and safety should be a top national priority, the time the federal government continues to spend on CISA demonstrates that’s not the case. Threat intelligence is already being shared bountifully. It is the processing of that information, the application of that information, the operationalizing [sic] of that information, and finally the incorporation of that information into an overarching cyber strategy and risk mitigation platform that is sorely lacking. Threat intelligence sharing is not the problem.”

CISA is also criticized for lacking clarity – the bill does not specifically define just how the information will be shared or managed. Nowhere in the bill does it disallow shared information from being used outside the scope of cybercrime investigations. On the wake of Edward Snowden’s disclosures, passing a bill that allows the NSA to gather personal information even easier, could be seen as ironic.

For those of you unfamiliar with Edward Snowden, Snowden revealed thousands of documents exposing the US governments vast reach of information gathering. Ex-NSA contractor Snowden is currently hiding in Russia and according to this CNN article, he criticizes CISA, commenting that the FBI and NSA already collect this kind of hacking data all over the internet, but CISA would allow them to collect even more directly from companies.

Recap

This bill may have good intentions, but due to its vagueness, it can be very costly and may cause problems. Some view it as progress but many view it as just another infraction on our right to privacy. Currently, CISA has only made it through the Senate and now must be combined with several other cyber security bills at the House and finally, the President must sign off on it. However, the Obama Administration has already made it clear that they support the bill.