MiniPlasma, a Powerful LPE
Researchers have identified two security vulnerabilities, YellowKey and GreenPlasma, affecting Windows systems. YellowKey involves the 'autofstx.exe' binary present in Windows Update and WinRE images, potentially enabling controlled file deletion during updates. GreenPlasma may allow elevation of privilege by writing to protected registry keys, with evidence suggesting the flaw remains unpatched in current Windows 11 versions.
- ▪The YellowKey vulnerability is linked to the 'autofstx.exe' binary, which propagates transaction files across volumes.
- ▪'autofstx.exe' is present in Windows Update and WinRE images, raising concerns that disabling WinRE may not mitigate the issue.
- ▪A technique inspired by a Google Project Zero finding was found to reproduce an elevation of privilege vulnerability in fully patched Windows 11 and Insider Preview systems.
- ▪The GreenPlasma issue could hypothetically allow writing to another user's registry hive, representing a security boundary violation.
- ▪A proof-of-concept for CVE-2020-17103 was uploaded to GitHub after being shared with Google Project Zero.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Blogspot |
| Canonical URL | https://deadeclipse666.blogspot.com/2026/05/ |
| Publication time | Sat, 16 May 2026 14:29:31 +0000 |
| Retrieval time | 2026-05-16T14:40:18.792Z |
| Last seen | 2026-05-16T14:40:18.792Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | cRDWOpoWYEQJ · 2 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
-----BEGIN PGP SIGNED MESSAGE-----Hash: SHA512Recently two researchers had interesting discoveries regarding YellowKey and GreenPlasma,The YellowKey is caused by the binary "autofstx.exe" which propagates all present volumes for transaction files, a researcher (unsure if they want to be named) told me that this binary is also present in windows update WinRE images and I think they will definitely have the same vulnerability as well. However, I'm unsure if it's possible to trigger the controlled file deletion when windows is updating.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Blogspot.
Discussion
0 commentsMore from Blogspot
