CVE-2010-2568: Microsoft Windows Remote Code Execution
Microsoft Windows · listed in the CISA catalog of actively exploited vulnerabilities since 2022-09-15.
- CVSS v3.1 (CISA ADP)
- 7.8
- high
- EPSS (exploit probability, 30 days)
- 90%
- higher than 99.7% of all CVEs
- Added to CISA KEV
- 2022-09-15
- US federal due date 2022-10-06
- Automatable (CISA SSVC)
- no
- technical impact: total
CVE-2010-2568 explained
CVE-2010-2568 is a remote code execution vulnerability in the Windows Shell of Microsoft Windows. Crafted .LNK or .PIF shortcut files are not properly handled during icon display in Windows Explorer, allowing arbitrary code execution. It was demonstrated in the wild in July 2010 and is listed in CISA's Known Exploited Vulnerabilities catalog.
Impact
Local users or remote attackers can execute arbitrary code when Windows Explorer displays the icon of a crafted shortcut file. No privileges are needed, but user interaction is required. Successful exploitation fully compromises confidentiality, integrity and availability. CISA rates the technical impact as total, meaning full control of the affected component. CISA rates it as not automatable. Attackers are known to exploit it, and it was originally reported with malware targeting Siemens WinCC SCADA systems.
Who is affected
The description names Windows Shell in Microsoft Windows XP SP3, Server 2003 SP2, Vista SP1 and SP2, Server 2008 SP2 and R2, and Windows 7. The CVE record itself lists no affected version entries for Microsoft Windows. The CVE record names no fixed version. Consult the Microsoft advisory for the updates that address this issue.
Written with AI from the data on this page and checked against it automatically.
Official description
Windows Shell in Microsoft Windows XP SP3, Server 2003 SP2, Vista SP1 and SP2, Server 2008 SP2 and R2, and Windows 7 allows local users or remote attackers to execute arbitrary code via a crafted (1) .LNK or (2) .PIF shortcut file, which is not properly handled during icon display in Windows Explorer, as demonstrated in the wild in July 2010, and originally reported for malware that leverages CVE-2010-2772 in Siemens WinCC SCADA systems.
CISA required action: Apply updates per vendor instructions.
CISA notes
How to fix it
- The CVE record names no fixed version – check the vendor advisory and CISA's required action for updates and mitigations.
- Vendor advisory: microsoft.com/technet/security/advisory/2286198.mspx
- CISA's deadline for US federal agencies: 2022-10-06 (passed) – a useful benchmark for everyone else, too.
What to do
- Apply the Microsoft security updates for this vulnerability per vendor instructions.
- Identify systems running the affected Windows versions named in the description and confirm they are patched.
- Replace systems that can no longer receive Microsoft updates with supported Windows versions.
- Restrict untrusted shortcut files from removable media and network shares until systems are patched.
- Check exposed systems, including those connected to SCADA environments, for signs of compromise.
The CVE record names no fixed version. Follow the Microsoft advisory and CISA's required action to apply updates per vendor instructions. Until updates are confirmed on every system, limit exposure to untrusted shortcut files from removable media and network shares, and monitor for signs of compromise.
Written with AI from the data on this page and checked against it automatically.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- No – each attack needs manual steps
- Technical impact
- Total – full control of the component or total information disclosure
Weakness: CWE-20
Questions about CVE-2010-2568
- Is CVE-2010-2568 being exploited?
- Yes. It was demonstrated in the wild in July 2010, and CISA added it to its Known Exploited Vulnerabilities catalog on 2022-09-15. Whether it is used in ransomware campaigns is unknown.
- What is the deadline for US federal agencies?
- CISA set a US federal due date of 2022-10-06. The required action is to apply updates per vendor instructions.
- Does a user need to open the malicious file?
- User interaction is required. The flaw is triggered when Windows Explorer displays the icon of a crafted .LNK or .PIF shortcut file.
Written with AI from the data on this page and checked against it automatically.
References
Trackers and catalogs
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-22. Always confirm with the vendor's or distribution's advisory before patching.