|
Patch is available from Microsoft, see references below for more information.
New Signature published in XPU 30.080:
2286198 - LNK_MsWin_Code_Execution (attack - will not have blocking enabled)
New signatures published in XPU 30.071:
2110223 - HTTP_Lnk_File_Accessed (attack - will not have blocking enabled) 2110224 - Email_Lnk_File_Attachment (attack- will not have blocking enabled) 2110225 - FTP_Lnk_File_Accessed (attack- will not have blocking enabled) 3110037 - LNK_File_Detected (audit) 3110038 - SMB_Lnk_File_Accessed (audit)
All of these are audit/anomaly type signatures and are not necessarily indicative of attack. However, if enabled, they will detect attacks. Blocking is NOT enabled by default on any of the existing signatures due to the high risk of false alarms. Signatures published in XPU 30.071 are monitoring transfers of shortcut files through these listed protocols.
Early signatures published and announced:
IBM Security has three signatures that will detect .LNK files traversing the network. (1) HTTP_FileTypeLnk (IssueID: 2002546) * This signature detects .LNK files passing over the HTTP (including WebDAV) protocol.
(2) FTP_FName_Lnk (IssueID: 2003609) * This signature detects the FTP transfer of a .LNK file.
(3) Email_Executable_Extension (IssueID: 2120020) * This signature blocks on the presence of LNK extensions. This has blocking by default.
The first (2) signatures do not block by default, as this type of activity is not necessarily malicious. However, it is relatively uncommon for .LNK files to be transferred over the network - and if you see them being transferred it's important to investigate. IBM X-Force suggests that customers who are concerned with the vulnerability described in CVE-2010-2568 enable blocking for those signatures until a vendor supplied patch is available.
IBM X-Force will continue to actively research this vulnerability and monitor the Internet for potential attack activity. We will update this alert for our customers as more information becomes apparent.
|