Monday, December 2, 2024
HomeCyber Security NewsWindows Server 2012 0-day Vulnerability Exposes Critical Security Flaw

Windows Server 2012 0-day Vulnerability Exposes Critical Security Flaw

Published on

SIEM as a Service

Cybersecurity researchers have identified a critical 0-day vulnerability in Windows Server 2012 and Server 2012 R2.

This previously unknown security flaw allows attackers to bypass the Mark of the Web (MoTW) verification on certain files, posing a significant threat to affected systems.

Vulnerability Details

The vulnerability, which was introduced over two years ago, has managed to evade detection despite the high level of scrutiny applied to Windows Server systems.

- Advertisement - SIEM as a Service

Even servers that have been fully updated with Extended Security Updates are vulnerable. This discovery underscores the persistent challenges in maintaining security in older software systems.

Leveraging 2024 MITRE ATT&CK Results for SME & MSP Cybersecurity Leaders – Attend Free Webinar

The researchers, who are holding back detailed information to prevent potential exploitation, have already notified Microsoft, as a report by 0Patch. They are awaiting an official fix from the tech giant, which could take time given the complexity of the issue.

In response to this critical security gap, the researchers have promptly issued micropatches.

These temporary fixes are being provided free of charge until Microsoft releases an official update. The micro patches cover the following configurations:

  • Legacy Windows Versions:
    • Windows Server 2012 updated to October 2023
    • Windows Server 2012 R2 updated to October 2023
  • Windows Versions Still Receiving Windows Updates:
    • Windows Server 2012 with Extended Security Updates
    • Windows Server 2012 R2 with Extended Security Updates

These patches have been seamlessly distributed to all affected computers with the 0patch Agent in PRO or Enterprise accounts.

Users can apply these micropatches without needing to reboot their systems, ensuring minimal disruption to operations.

The discovery of this vulnerability highlights the ongoing risk associated with unsupported Windows versions. Vulnerabilities are routinely identified and can be exploited by attackers aware of these security lapses.  

This proactive approach is crucial in maintaining security while awaiting a more permanent solution from Microsoft.

It emphasizes the importance of layered security strategies and the role of third-party solutions in closing gaps left by official updates.

Analyse Advanced Malware & Phishing Analysis With ANY.RUN Black Friday Deals : Get up to 3 Free Licenses.

Divya
Divya
Divya is a Senior Journalist at GBhackers covering Cyber Attacks, Threats, Breaches, Vulnerabilities and other happenings in the cyber world.

Latest articles

Amazon GuardDuty Enhanced With AI/ML Threat Detection Capabilities for Cloud Security

Amazon has taken a significant step forward to enhance the security of its cloud...

Linux 6.13-rc1 Released: What’s New!

In a recent announcement, Linus Torvalds, the creator of Linux, officially released the first...

Apple Safari JavaScriptCore Remote Code Execution Flaw Exploited in the Wild

A critical vulnerability identified as CVE-2024-44308 has been actively exploited in the wild, affecting...

MediaTek Processor Vulnerabilities Let Attackers Escalate Privileges

Several vulnerabilities affecting MediaTek processors have been identified, potentially allowing attackers to escalate privileges...

API Security Webinar

72 Hours to Audit-Ready API Security

APIs present a unique challenge in this landscape, as risk assessment and mitigation are often hindered by incomplete API inventories and insufficient documentation.

Join Vivek Gopalan, VP of Products at Indusface, in this insightful webinar as he unveils a practical framework for discovering, assessing, and addressing open API vulnerabilities within just 72 hours.

Discussion points

API Discovery: Techniques to identify and map your public APIs comprehensively.
Vulnerability Scanning: Best practices for API vulnerability analysis and penetration testing.
Clean Reporting: Steps to generate a clean, audit-ready vulnerability report within 72 hours.

More like this

Amazon GuardDuty Enhanced With AI/ML Threat Detection Capabilities for Cloud Security

Amazon has taken a significant step forward to enhance the security of its cloud...

Linux 6.13-rc1 Released: What’s New!

In a recent announcement, Linus Torvalds, the creator of Linux, officially released the first...

Apple Safari JavaScriptCore Remote Code Execution Flaw Exploited in the Wild

A critical vulnerability identified as CVE-2024-44308 has been actively exploited in the wild, affecting...