Sunday, February 9, 2025
HomeCVE/vulnerabilityActive Directory Domain Service Bug Let Attackers To Takeover Windows Domains

Active Directory Domain Service Bug Let Attackers To Takeover Windows Domains

Published on

SIEM as a Service

Follow Us on Google News

During the November 2021 Patch Tuesday Two Active Directory domain service privilege escalation security flaws have been detected recently by Andrew Bartlett of Catalyst IT, and these two security flaws allow hackers to take over Windows domains easily when they are united.

Microsoft suggested users to immediately patch these two Active Directory domain service privilege escalation security flaws that are tracked as:-

  • CVE-2021-42287: KDC bamboozling
  • CVE-2021-42278: SAM Name impersonation

Here’s what Microsoft stated:-

“This escalation attack allows attackers to easily elevate their privilege to that of a Domain Admin once they compromise a regular user in the domain. As always, we strongly advise deploying the latest patches on the domain controllers as soon as possible.”

In default configurations from standard Active Directory user to a Domain Admin can easily use the tool to escalate these privileges. While apart from this, for a given object several naming schemes are used by AD (Active Directory) and they are like:-

  • userPrincipalName (UPN)
  • sAMAccountName (SAM-Account)

How to find the sAMAccountNames?

To find the sAMAccountNames you have to follow some simple steps that we have mentioned below:-

  • First, you have to Click View option.
  • Then select the Advanced Features.
  • After that, you have to open the properties of an object.
  • Then Attribute Editor tab.
  • Lastly, scroll down to sAMAccountName.

Identify Potential Compromised Computers

To identify potentially compromised systems and servers Microsoft has shared detailed guidance, and here we have mentioned them below:-

  • The sAMAccountName change is based on event 4662. Please make sure to enable it on the domain controller to catch such activities.
  • Open Microsoft 365 Defender and navigate to Advanced Hunting.
  • Copy the following query:-

IdentityDirectoryEvents

| where Timestamp > ago(1d)

| where ActionType == “SAM Account Name changed”

| extend FROMSAM = parse_json(AdditionalFields)[‘FROM SAM Account Name’]

| extend TOSAM = parse_json(AdditionalFields)[‘TO SAM Account Name’]

| where (FROMSAM has “$” and TOSAM !has “$”)

        or TOSAM in (“DC1”, “DC2”, “DC3”, “DC4”) // DC Names in the org

| project Timestamp, Application, ActionType, TargetDeviceName, FROMSAM, TOSAM, ReportId, AdditionalFields

  • Replace the marked area with the naming convention of your domain controllers.
  • Run the query and analyze the results which contain the affected devices.
  • Thoroughly examine all the compromised computers and servers to determine whether they have been weaponized or not.

By following the above steps you can easily identify potentially compromised systems and servers to take proper mitigations to avoid such attacks in the future.

You can follow us on Linkedin, Twitter, Facebook for daily Cybersecurity and hacking news updates.

Balaji
Balaji
BALAJI is an Ex-Security Researcher (Threat Research Labs) at Comodo Cybersecurity. Editor-in-Chief & Co-Founder - Cyber Security News & GBHackers On Security.

Latest articles

UK Pressures Apple to Create Global Backdoor To Spy on Encrypted iCloud Access

United Kingdom has reportedly ordered Apple to create a backdoor allowing access to all...

Autonomous LLMs Reshaping Pen Testing: Real-World AD Breaches and the Future of Cybersecurity

Large Language Models (LLMs) are transforming penetration testing (pen testing), leveraging their advanced reasoning...

Securing GAI-Driven Semantic Communications: A Novel Defense Against Backdoor Attacks

Semantic communication systems, powered by Generative AI (GAI), are transforming the way information is...

Cybercriminals Target IIS Servers to Spread BadIIS Malware

A recent wave of cyberattacks has revealed the exploitation of Microsoft Internet Information Services...

Supply Chain Attack Prevention

Free Webinar - Supply Chain Attack Prevention

Recent attacks like Polyfill[.]io show how compromised third-party components become backdoors for hackers. PCI DSS 4.0’s Requirement 6.4.3 mandates stricter browser script controls, while Requirement 12.8 focuses on securing third-party providers.

Join Vivekanand Gopalan (VP of Products – Indusface) and Phani Deepak Akella (VP of Marketing – Indusface) as they break down these compliance requirements and share strategies to protect your applications from supply chain attacks.

Discussion points

Meeting PCI DSS 4.0 mandates.
Blocking malicious components and unauthorized JavaScript execution.
PIdentifying attack surfaces from third-party dependencies.
Preventing man-in-the-browser attacks with proactive monitoring.

More like this

Microsoft Sysinternals 0-Day Vulnerability Enables DLL Injection Attacks on Windows

A critical zero-day vulnerability has been discovered in Microsoft Sysinternals tools, posing a serious security threat...

7-Zip 0-Day Flaw Added to CISA’s List of Actively Exploited Vulnerabilities

The U.S. Cybersecurity and Infrastructure Security Agency (CISA) has added a critical 0-day vulnerability...

Logsign Vulnerability Allows Remote Attackers to Bypass Authentication

A critical security vulnerability has been identified and disclosed in the Logsign Unified SecOps...