CVE-2010-2568

Known Exploited Public Exploit

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.

7.8

CVSS

Severity: High

CVSS 3.1 •

CVSS 2.0 •

EPSS 93.48% Top 5%

KEV Since

Vendor Advisory microsoft.com Vendor Advisory secunia.com Vendor Advisory microsoft.com

Affected: n/a n/a

References

Link	Tags
http://www.us-cert.gov/cas/techalerts/TA10-222A.html	third party advisory us government resource
http://isc.sans.edu/diary.html?storyid=9181	issue tracking exploit
https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A11564	vdb entry signature broken link
http://www.f-secure.com/weblog/archives/00001986.html	not applicable
http://www.kb.cert.org/vuls/id/940193	us government resource third party advisory patch
http://krebsonsecurity.com/2010/07/experts-warn-of-new-windows-shortcut-flaw/	press/media coverage
http://secunia.com/advisories/40647	third party advisory vendor advisory
http://www.microsoft.com/technet/security/advisory/2286198.mspx	broken link patch vendor advisory
http://isc.sans.edu/diary.html?storyid=9190	issue tracking
http://www.securityfocus.com/bid/41732	exploit vdb entry third party advisory broken link
http://www.f-secure.com/weblog/archives/new_rootkit_en.pdf	exploit
https://www.geoffchappell.com/notes/security/stuxnet/ctrlfldr.htm	third party advisory
http://securitytracker.com/id?1024216	vdb entry third party advisory broken link
https://docs.microsoft.com/en-us/security-updates/securitybulletins/2010/ms10-046	patch vendor advisory

Frequently Asked Questions

What is the severity of CVE-2010-2568?: CVE-2010-2568 has been scored as a high severity vulnerability.
How to fix CVE-2010-2568?: To fix CVE-2010-2568, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2010-2568 being actively exploited in the wild?: It is confirmed that CVE-2010-2568 is actively exploited. Be extra cautious if you are using vulnerable components. According to its EPSS score, there is a ~93% probability that this vulnerability will be exploited by malicious actors in the next 30 days.