Posted on

EternalBlue: The Vulnerability That Changed Cybersecurity Forever

Hello, aspiring ethical hackers. In this article, you will learn about the infamous EternalBlue vulnerability and its impact in detail. In the world of cybersecurity, some vulnerabilities are remembered not just for how they worked, but for the damage they caused. EternalBlue is one such vulnerability. It played a major role in some of the most destructive cyberattacks in history and serves as an important lesson for anyone beginning their cybersecurity journey.

This article explains what EternalBlue is, why it was so dangerous, how it was abused and what beginners should learn from it.

What is EternalBlue?

EternalBlue is the name given to a critical vulnerability in Microsoft Windows that affected the Server Message Block version 1 (SMBv1) protocol. SMB is used by Windows systems to share files, printers and other resources across a network.

The vulnerability allowed attackers to send specially crafted network messages to a Windows machine and execute code remotely without needing a username or password. This made it a remote code execution (RCE) vulnerability, one of the most serious types in cybersecurity.

Why EternalBlue Was So Dangerous?

EternalBlue stood out because of a few key characteristics:

  • It required no user interaction
  • It worked over the network
  • It allowed full system compromise
  • It could spread automatically between systems

In simple terms, a vulnerable computer could be compromised just by being connected to a network. This made it ideal for worm-like attacks, where malware spreads rapidly from one system to another.

How EternalBlue Became Public?

It is alleged that EternalBlue was originally developed as a cyber weapon and kept secret. In 2017, it was leaked publicly, exposing a powerful attack technique to the world. Once released, attackers quickly integrated this vulnerability into malware, ransomware and automated attack tools. Even though Microsoft released security updates, many systems remained unpatched, creating a large pool of vulnerable targets.

Real-World Attacks That Used EternalBlue

The most famous attacks linked to EternalBlue include,

WannaCry Ransomware:

WannaCry spread rapidly across the globe in 2017, encrypting files and demanding ransom payments. It used EternalBlue to move automatically from one Windows system to another, causing massive disruption to hospitals, businesses and governments.

NotPetya:

NotPetya also leveraged EternalBlue to spread inside corporate networks. Unlike typical ransomware, its primary goal was destruction, not profit. These attacks showed how a single vulnerability could cause global-scale damage.

Why EternalBlue Still Matters Today?

Even years after its disclosure, this vulnerability remains relevant for beginners to study. Reasons include:

  • Many legacy systems still exist
  • Some networks still expose SMB services
  • Poor patch management remains common
  • The vulnerability represents a perfect storm of design flaws and operational failures

EternalBlue reminds us that unpatched systems are a long-term risk, not a short-term problem.

What Beginners Should Understand About EternalBlue?

For cybersecurity beginners, this vulnerability is not about learning how to exploit systems. Instead, it teaches:

  • Why vulnerabilities are classified as “critical”
  • How one flaw can enable large-scale attacks
  • The importance of defense over offense
  • Why security basics matter more than advanced tools

Understanding EternalBlue builds strong foundational thinking.

Proof of Concept

As the vulnerability is so famous (I mean infamous), Metasploit has already released exploit modules for this particular vulnerability.

We are going to test some of these modules on a Windows 7 target. Let’s first use the scanner module of metasploit to test whether this machine is vulnerable to EternalBlue vulnerability.

Set the RHOSTS option and execute the module.

The scanner module confirms that the target is indeed vulnerable. Now, let’s load the module for exploiting Eternal Blue vulnerability and grab a session.

Set all the required options and use “check” command to see if the target is indeed vulnerable.

After all the required options are set, execute the module.

eternalblue

As you can see, we got a meterpreter session on the target system and that too with SYSTEM privileges.

Lessons to defenders from EternalBlue

EternalBlue taught the cybersecurity community several critical lessons. They are,

1. Patch Management Is Essential:

Microsoft released patches before the major attacks occurred. Systems that were updated were protected. Those that weren’t suffered the consequences.

2. Legacy Protocols Are Dangerous:

SMBv1 was outdated and insecure. Disabling unnecessary legacy protocols reduces attack surface.

3. Network Segmentation Matters:

Flat networks allowed malware to spread rapidly. Segmentation can limit the impact of a breach.

4. Exposure Equals Risk:

Services exposed to networks, especially the internet must be carefully controlled and monitored.

Conclusion

EternalBlue is a landmark vulnerability in cybersecurity history. It demonstrated how a single flaw, combined with poor patching and legacy systems could cripple organizations worldwide.

For beginners, EternalBlue is a reminder that cybersecurity is not just about advanced hacking techniques. Often, the most devastating attacks succeed because basic security practices were ignored.

Posted on

Beginners guide to Follina vulnerability

Hello aspiring ethical hackers. In this article, you will learn about Follina vulnerability, a critical zero-day vulnerability discovered in Microsoft Office in 2022.

About the vulnerability

Follina tracked with CVE-ID CVE-2022-30190 is the name given to a remote code execution (RCE) vulnerability in Microsoft Office and Microsoft Support Diagnostic Tool (MSDT). Microsoft Support Diagnostic Tool (MSDT) is a service used for gathering diagnostic data about the system.

Follina is the name of a municipality that is located 60 kms northwest of Venice in Italy. Completely unrelated, the vulnerability has been named Follina as the malicious file was referencing to an executable that was named 0438. This is the area code of Follina, hence the zero-day has been named so.

A link to a HTML file on remote target that uses the ms-msdt: protocol handler is placed in a specially crafted Word document (.docx). When this .docx file is opened (or sometimes just previewed), the document causes Word to load and execute the malicious MSDT payload. This bypasses many traditional security defenses (like macros being disabled) and no user interaction beyond opening the file is necessary in some cases.

This vulnerability allows a remote attacker to use a Microsoft Office document template to execute code via MSDT and download a malicious payload from a remote URL. It affects Office 2013, 2016, 2019, 2021, Office ProPlus and Office 365.  

Mitigation and Patches

Microsoft initially suggested a workaround and later released a patch for this vulnerability in June 2022 (via Windows Update).

Proof Of Concept

Let’s see PoC exploit for Follina practically. We are doing this on Klai Linux. For this let’s download a exploit from GitHub. Navigate into the cloned directory and you will see files as shown below.

Two files are important in this directory. The “clickme.docx” is the file that uses MSDT to connect to a remote website and execute the exploit. The exploit is present in the “exploit.html” file. If this POC is successful, the exploit will popup calc.exe.

I tested this exploit on MS Office 2019 running on Windows 10. I hosted the exploit using WAMP server running on localhost.

I opened the clickme.doc and waited. Nothing happened. Then I saved it as clickme.rtf file as shown below.

This time when I clicked on clickme.rtf file, this happened,

And the calculator popped up. The Proof Of Concept Is successful.

follina
Posted on

Beginners guide to PrintNightmare vulnerability

Hello, aspiring ethical hackers. In our previous blogpost, you learnt about EternalBlue vulnerability. In this article, you will learn about another critical vulnerability called PrintNightmare vulnerability.

What is PrintNightmare vulnerability?

PrintNightmare is a vulnerability that affects the Microsoft’s Windows operating systems. This vulnerability is present in the print spooler service of Microsoft Windows. The printer spooler service is used for printing services and is turned on by default. The versions of Windows vulnerable to PrintNightmare include Windows 7 to Windows 10 and windows Server 2008 to the latest version of Windows Servers.

Proof of Concept (PoC)

The PrintNightmare vulnerability has two variants : one allows unauthorized remote code execution (CVE-2021-34527) and the other allows unauthorized privilege escalation (CVE-2021-1675). In this article, readers will see a proof of concept for exploiting the privilege escalation vulnerability. For this, we will use Windows 10 version 1809 as target system. The PowerShell Script we used in this demo can be downloaded from GitHub.

In this scenario, let’s imagine I already have access to the target machine as a user with low privileges. The first thing we have to do is to confirm if the printer spooler service is running on the target system or not. This can be done using PowerShell command given below.

"Get-Service -Name "spooler""

The print spooler service is running on the target system. As you can see in the images below, I am running as a user with very limited privileges.

Next, I download the PowerShell script and import it using command shown below.

Import-Module .\<script Name>

Once the module is successfully imported, I execute the script with command to create a new user as shown below.

"Invoke-Nightmare -NewUser "<username to create>" -NewPassword  <password for that new user> DriverName "PrintMe""


This command will create a new user on the target system with administrator privileges.

How to exploit printnightmare

In the image above, you can see that a new user named “hacker” has been created. Now, let’s check the privileges of this user.

As you can see, the new user we created belongs to the local administrators group. You can login as that user.

The PoC is successful.