- ITDM 2025 전망 | “비전을 품은 기술 투자, 모두가 주춤한 시기에 진가 발휘할 것” 컬리 박성철 본부장
- The Model Context Protocol: Simplifying Building AI apps with Anthropic Claude Desktop and Docker | Docker
- This robot vacuum and mop performs as well as some flagship models - but at half the price
- Finally, a ThinkPad model that checks all the boxes for me as a working professional
- Why I recommend this Android phone for kids over a cheap Samsung or Motorola model
Microsoft Assigns CVE to PrintNightmare but no CVSS Score
The zero-day vulnerability known as PrintNightmare now has an official CVE listing, but Microsoft is still investigating the severity of the bug.
The public disclosure of the flaw came about in a comedy of errors this week. A Chinese research team at QiAnXin announced exploit code for a similar remote code execution (RCE) vulnerability in the Windows Print Spooler service (CVE-2021-1675), which Microsoft had patched in June.
Mistaking this code for a project that they had been working on, researchers at Shenzhen-based Sangfor Technologies decided to release a proof-of-concept exploit code they were due to announce at Black Hat USA in August.
However, the bug they discovered, PrintNightmare, was completely new, and this zero-day has now been widely circulated.
Microsoft yesterday named it as CVE-2021-34527.
“A remote code execution vulnerability exists when the Windows Print Spooler service improperly performs privileged file operations,” it explained.
“An attacker who successfully exploited this vulnerability could run arbitrary code with system privileges. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.”
Security researchers have warned that the vulnerability could allow authenticated actors to hijack domain controllers, which would effectively give them the keys to the kingdom to deploy ransomware or other malware across victim networks.
Therefore, while Microsoft said it is still investigating the severity of the CVE, it would be a surprise if it was not labeled “critical.”
Although the code containing the vulnerability is in all versions of Windows, Microsoft said it is also still looking into whether all versions are exploitable.
In the meantime, it has recommended affected organizations check if they have Print Spooler running and disable it. However, this will also disable the ability to print both locally and remotely.