Skip to main content

Insider threat - The average insider threat attack scenario. How attackers can take over an entire domain in a few steps. Part 2.

Illustration of Insider threat - The average insider threat attack scenario. How attackers can take over an entire domain in a few steps. Part 2.
DOMINIK ANTOŃCZAK

Have you ever wondered how little it takes to take over an Active Directory domain? Have you considered using some exploit? Nah, using exploits is not a fancy way and can be easily detected, and if anything, that option remains as a last resort. As savvy “hackers”, we possess the right knowledge to navigate the network smoothly without making noise. Sometimes it takes a few steps, and just as Neil Armstrong said, it’s one small step for man…, but for us hackers, taking over one system is a small step towards taking over the entire network. In this scenario, I’ll demonstrate how the ability to analyze acquired information, coupled with a few sublime actions, was sufficient to take over the entire domain of a company consisting of 500-1000 users.

As an advanced attacker, I already have access to the “unhackable.corp” LAN and I start by analyzing what’s on the local network. I always like to check what is in the shared directories because you can always find very, very interesting things there, just like in this case. The “dev” directory, the first thing that comes to mind is “ah, the DEV directory, source code, access data, configuration files”, so I’ll probably be able to get some data from this directory.

Dev directory contents

In this directory, there are about 30 folders. The first one that caught my attention is AWS, and what I found in it I didn’t expect at all.

AWS directory

If you didn’t say, “Oh, here may be the passwords for some AD account”, then you need more practice ;).

And this time my intuition didn’t fail me - domain account credentials.

Domain credentials

Time to see what the user “serverdeveloper” has to offer in the attacked AD. Ideally suited for this purpose is BloodHound, a graphical tool that reveals any connections within Active Directory. Mmmm, and such links are more than welcome. Time to extract secrets from the A-SAP92 system.

BloodHound analysis

Oh, and there are credentials for another AD account. This time, the name suggests that I’m dealing with a user who can potentially cause quite a stir in the AD.

Backup admin credentials

I’ll tell you, when it comes to “stars”, only these will do:

Domain Admins group

The user backupadmin is in the Domain Admins group - how nice… :)

Now, just like in Mortal Kombat, it’s time to use the right combination to execute a fatality: a DCSync, which will dump all secrets from the domain controller:

DCSync execution

Great, in a few steps, I managed to take over the entire network of the unhackable.corp company. As an additional tidbit for the keen reader, I’ll mention that the percentage of cracked hashes was 15.08%, with 232 unique passwords out of 1538 available, granting access to 323 accounts. It may not be a lot but considering that each of the 323 users can take over the entire AD in their own way, it’s quite an interesting result.

Other Insights

Illustration of Server shutdown via GraphQL during real-life pentest

Server shutdown via GraphQL during real-life pentest

KAMIL JAROSIŃSKI

GraphQL is a query language and environment created by Facebook in 2012 and released publicly in 2015. However, it has only gained significant popularity among developers and organizations in the last few years. Why is it so popular? GraphQL serves as an alternative to traditional API protocols, like REST, offering a more flexible and efficient way for client-server communication. The emergence of new technology opens up new perspectives and solves some problems, but unfortunately, it also introduces threats. This is the case with GraphQL. If used without proper knowledge, it could potentially allow for a DoS (Denial of Service) attack.

READ article
Illustration of Persistent threats via blind XSS and subsequent data exfiltration - tips and ticks from a security perspective.

Persistent threats via blind XSS and subsequent data exfiltration - tips and ticks from a security perspective.

SEBASTIAN JEŻ, KALINA ZIELONKA

A sneaky security threat that combines Blind XSS with data exfiltration techniques poses a significant risk, allowing adversaries to insert persistent HTML/JavaScript code that executes within the domain context of an application. This vulnerability can be exploited to steal any data from the application or perform actions on behalf of another user.

READ article
A professional cybersecurity consultant ready to assist with your inquiry.

Any questions?

Happy to get a call or email
and help!