/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

← → days · ↑ ↓ browse · Enter similar · o open

Researchers detail two new local privilege escalation vulnerabilities, one in recent builds of Windows 10 and the preview of Windows 11, and the other in Linux

Both OSes have flaws that allow attackers with a toehold to elevate access.  —  The world woke up on Tuesday to two new vulnerabilities … Source: US-CERT , Qualys Security Blog , and Qualys Security Blog .

Ars Technica Dan Goodin

Context & Ripple Effects

The disclosures fit a longer record of local escalation weaknesses in both platforms: Linux researchers had previously exposed an aging kernel privilege-escalation flaw, while Microsoft had already patched a Windows kernel zero-day and faced a separate Windows 10 escalation exploit in 2019.

The new reports matter because they make an attacker’s initial foothold more valuable across Windows and Linux. A released patch for Linux’s CopyFail issue creates an immediate remediation path, while the Windows 10 and Windows 11 preview findings put attention on privilege boundaries in current and forthcoming Windows builds.

First-order effects

  • Linux administrators can apply the CopyFail patch to remove a route by which unprivileged local users could obtain root access.
  • Windows 10 users and Windows 11 preview testers face local flaws that can turn an existing foothold into elevated access, increasing the impact of any initial compromise.

Second-order effects

  • Microsoft’s Windows 11 preview testing must account for an elevation path affecting recent Windows code, rather than treating the exposure as confined to an older release.
  • Security teams running mixed Windows and Linux estates need to prioritize local-access controls and patch deployment, since the disclosed flaws affect the post-compromise stage on both platforms.

Third-order effects

  • Repeated kernel, filesystem, and local-access findings point to privilege boundaries as a persistent operating-system security battleground, with patch speed determining how long an initial foothold can become full control.
  • If this pattern continues, OS vendors will be judged not only on preventing initial intrusion but on how reliably they contain a compromised local account before attackers reach administrator or root privileges.

The trend: Operating-system security is increasingly shaped by the race to prevent low-privilege footholds from becoming system-level control through local escalation flaws.

Discussion

  • @jonaslyk Jonas L on x
    yarh- for some reason on win11 the SAM file now is READ for users. So if you have shadowvolumes enabled you can read the sam file like this: I dont know the full extent of the issue yet, but its too many to not be a problem I think. https://twitter.com/...
  • @gossithedog Kevin Beaumont on x
    Added US-CERT vulnerability note for this, written by @wdormann. It's excellent and clearly lays out the problem. #HiveNightmare #SeriousSAM https://www.kb.cert.org/... https://twitter.com/...
  • @qualys @qualys on x
    CVE-2021-33910: Denial of Service (Stack Exhaustion) in systemd (PID 1): Any unprivileged user can exploit this vulnerability to crash systemd and hence the entire operating system (a kernel panic). https://blog.qualys.com/...
  • @bad_packets Bad Packets on x
    “Starting with Windows 10 build 1809, non-administrative users are granted access to SAM, SYSTEM, and SECURITY files. This can allow for local privilege escalation (LPE).” https://www.kb.cert.org/...
  • @jeffmcjunkin Jeff McJunkin on x
    Alert: Windows 10/11 is vulnerable to privilege escalation due to a permissions flaw. No CVE as of yet. @wdormann of @certcc has a comprehensive write-up: https://www.kb.cert.org/... W/o a @msftsecurity fix, I'd recommend checking your exposure and focusing on detective controls.
  • @wdormann Will Dormann on x
    I don't predict myself making a flowchart to give you an answer to whether or not you're vulnerable, as there seem to be too many variables. Just check for yourself to be sure! I've published VU#506989 on this issue: https://www.kb.cert.org/...
  • @sergeybratus Sergey Bratus on x
    So a parser bug in systemd will crash Linux https://blog.qualys.com/... . Classic insecurity pattern: put ad hoc parsers in a critical OS component that can't recover. Usually we isolate such components with firewalls. Perhaps it's time for a firewall for systemd? :)