Anti - Security Un projet qui vous tiendra @coeur...

Experts Warn of New Windows Shortcut Flaw

Questions, réponses, sujets divers, news et informations

Experts Warn of New Windows Shortcut Flaw

Nouveau messagede x[@♥] » Ven 16 Juil 2010 07:56

Experts Warn of New Windows Shortcut Flaw

Le retour de l'autorun! Enfin, presque...

Researchers have discovered a sophisticated new strain of malicious software that piggybacks on USB storage devices and leverages what appears to be a previously unknown security vulnerability in the way Microsoft Windows processes shortcut files.

VirusBlokAda, an anti-virus company based in Belarus, said that on June 17 its specialists found two new malware samples that were capable of infecting a fully-patched Windows 7 system if a user were to view the contents of an infected USB drive with a common file manager such as Windows Explorer.

USB-borne malware is extremely common, and most malware that propagates via USB and other removable drives traditionally has taken advantage of the Windows Autorun or Autoplay feature. But according to VirusBlokAda, this strain of malware leverages a vulnerability in the method Windows uses for handling shortcut files.

Shortcut files — or those ending in the “.lnk” extension — are Windows files that link (hence the “lnk” extension) easy-to-recognize icons to specific executable programs, and are typically placed on the user’s Desktop or Start Menu. Ideally, a shortcut doesn’t do anything until a user clicks on its icon. But VirusBlokAda found that these malicious shortcut files are capable of executing automatically if they are written to a USB drive that is later accessed by Windows Explorer.

“So you just have to open infected USB storage device using [Windows] Explorer or any other file manager which can display icons (for i.e. Total Commander) to infect your Operating System and allow execution of the malware,” wrote Sergey Ulasen, an anti-virus expert with the company, in an advisory published this month.

Ulasen said the malware installs two drivers: “mrxnet.sys” and “mrxcls.sys.” These so-called “rootkit” files are used to hide the malware itself so that it remains invisible on the USB storage device. Interestingly, Ulasen notes that both driver files are signed with the digital signature of Realtek Semiconductor Corp., a legitimate hi-tech company.

Ulasen said he reached out to Microsoft and to Realtek but got a response from neither. Jerry Bryant, group manager of response communications at Microsoft, told KrebsOnSecurity.com Wednesday that “Microsoft is investigating new public claims of malware propagating via USB storage devices. When we have completed our investigations we will take appropriate action to protect users and the Internet ecosystem.”

If this truly is a new vulnerability in Windows, it could soon become a popular method for spreading malware. But for now, this threat seems fairly targeted: Independent security researcher Frank Boldewin said he had an opportunity to dissect the malware samples, and observed that they appeared to be looking for Siemens WinCC SCADA systems, or machines responsible for controlling the operations of large, distributed systems, such as manufacturing and power plants.

“Looks like this malware was made for espionage,” Boldewin said.


Src here!

"J'aime" ce genre de nouvelles. je me souviens parfaitement de la volonté de Microsoft d'oter la fonctionnalité de l'autorun (.inf) de ses OS (à partir de Vista).

En effet, pour un quelconque système de stockage (C:\, D:\, lecteur amovible, carte SD, CDROM...) il est possible d'y placer un jolie fichier texte autorun.inf contenant quelques brèves instructions pour par exemple lancer un exécutable dès l'ouverture du support, ou placer un icône représentatif du support (dans poste de travail par exemple).

Sympathique à première vue! Mais une magnifique brèche pour déployer des vers et backdoor. Suite à la suppression de l'activation de cette fonctionnalité par défaut dans les nouveaux Windows, les pirates ont réussi à partir du simple shortcut (icône) à faire un RCE et donc exécuter du code arbitraire sur la machine. Et BIM! On est reparti pour un tour!

Vis-à-vis des autoruns, je tiens tout de même à vous donner quelques petits conseils, notamment pour ceux usant encore de Windows XP, ou ceux qui trimballent encore des clés USB souvent ou occasionnellement connectée à Windows XP.

J'ai remarqué il y a 1-2 mois un très jolie vers dynamique et polymorphe qui passe au travers d'un grand nombre d'antivirus. Celui-ci se propage par le biais des supports amovibles et autorun. Ainsi il n'est pas effectif sur Vista, 7 ou server 2008, mais il tourne parfaitement sur les versions antérieures.

Pour le déceller? Un processus bizarre était apparu dans mon taskman, des ports bizarres étaient visibles via un "netstat -na" bref, ça m'a mis la puce à l'oreille.

Pour s'en débarrasser, la c'est la galère. Car à chaque lancement, il se redéploi. Commencez par afficher tous les fichiers systèmes et archives qui se trouvent à la racine de tous vos lecteurs (ce sont des fichiers invisibles à l'utilisateur, même lorsque que "afficher les fichiers cachés" est activé).

Démarrer / Exécuter / "cmd.exe"

Allez à la racine de chacun de vos lecteurs, puis supprimez tous les attributs des fichiers s'y trouvant (inoffensif) :

Code: Tout sélectionner
C:\blabla\>c:
C:\>attrib -s -h -r -a *
C:\>d:
D:\>attrib -s -h -r -a *
D:\>e:
E:\>attrib -s -h -r -a *
[...]


La commande "attrib" permet de gérer les attributs optionnels des fichiers, notamment les fichiers cachés "h", systèmes "s", les archives "a" et la lecture seule "r". En précédant ces lettres d'un "-" on enlève l'attribut. Pour le remettre, remplacer par "+".

Ensuite, supprimez tous les fichiers autorun.inf se trouvant à toutes les racines (faites de même pour toutes vos clés USB).

Redémarrez votre système (puisqu'il n'y a plus aucun autorun.inf, le ver ne devrait plus se lancer) (un coup d'msconfig, de mode sans echec ou de killage de processus douteux est à envisager aussi ;)).

Puis une fois redémarrez, supprimer tout ce qui vous semble louche à la racine de vos lecteur (genre des exécutables douteux), ainsi que tout le contenu du répertoire temporaires (les vers se mettent aussi en copie ici régulièrement) accéssible via:

Démarrer / Exécuter / "%tmp%"

Voila, bonne journée!

:hat:
Temp...
Avatar de l’utilisateur
x[@♥]
 
Messages: 851
Inscription: Lun 21 Sep 2009 15:21
Localisation: Sur la root

Re: Experts Warn of New Windows Shortcut Flaw

Nouveau messagede x[@♥] » Lun 19 Juil 2010 07:38

L'exploit est paru :

Microsoft Windows Automatic LNK Shortcut File Code Execution



Code: Tout sélectionner
From: http://www.ivanlef0u.tuxfamily.org/?p=411

1. Unzip the files in 'C: \'. Start a DbgView or paste a KD to your VM.
2. Rename 'suckme.lnk_' to 'suckme.lnk' and let the magic do the rest of shell32.dll.
3. Look at your logs.

http://ivanlef0u.nibbles.fr/repo/suckme.rar
http://www.exploit-db.com/sploits/suckme.rar

Tested under XP SP3.

kd> g
Breakpoint 1 hit
eax=00000001 ebx=00f5ee7c ecx=0000c666 edx=00200003 esi=00000001 edi=7c80a6e4
eip=7ca78712 esp=00f5e9c4 ebp=00f5ec18 iopl=0         nv up ei pl nz na po nc
cs=001b  ss=0023  ds=0023  es=0023  fs=003b  gs=0000             efl=00000202
SHELL32!_LoadCPLModule+0x10d:
001b:7ca78712 ff15a0159d7c    call    dword ptr [SHELL32!_imp__LoadLibraryW (7c9d15a0)] ds:0023:7c9d15a0={kernel32!LoadLibraryW (7c80aeeb)}
kd> dd esp
00f5e9c4  00f5ee7c 000a27bc 00f5ee78 00000000
00f5e9d4  00000020 00000008 00f5ee7c 00000000
00f5e9e4  00000000 0000007b 00000000 00000000
00f5e9f4  00200073 002000e0 0000064c 0000028c
00f5ea04  1530000a 00000000 003a0043 0064005c
00f5ea14  006c006c 0064002e 006c006c 006d002e
00f5ea24  006e0061 00660069 00730065 00000074
00f5ea34  00090608 7c92005d 00000000 00000007
kd> db 00f5ee7c
00f5ee7c  43 00 3a 00 5c 00 64 00-6c 00 6c 00 2e 00 64 00  C.:.\.d.l.l...d.
00f5ee8c  6c 00 6c 00 00 00 92 7c-c8 f2 f5 00 00 17 72 02  l.l....|......r.
00f5ee9c  4b d2 00 00 d8 f2 f5 00-8b d2 a1 7c 00 00 00 00  K..........|....
00f5eeac  ac 80 9d 7c 30 d8 0d 00-34 d8 0d 00 b8 d7 0d 00  ...|0...4.......
00f5eebc  9a d2 a1 7c 30 d8 0d 00-c8 f2 f5 00 50 40 15 00  ...|0.......P@..
00f5eecc  50 40 15 00 00 00 00 00-b8 00 92 7c 40 b7 0c 00  P@.........|@...
00f5eedc  a8 ef f5 00 41 00 92 7c-18 07 09 00 5d 00 92 7c  ....A..|....]..|
00f5eeec  c8 f2 f5 00 00 ef f5 00-00 00 00 00 b8 00 92 7c  ...............|
kd> kv
ChildEBP RetAddr  Args to Child
00f5ec18 7ca81a74 00f5ee7c 000a27bc 00f5f2c4 SHELL32!_LoadCPLModule+0x10d (FPO: [1,145,4])
00f5ee50 7ca82543 00f5ee74 000a27bc 000a27c0 SHELL32!CPL_LoadAndFindApplet+0x4a (FPO: [4,136,4])
00f5f294 7cb56065 000a25b4 000a27bc 000a27c0 SHELL32!CPL_FindCPLInfo+0x46 (FPO: [4,264,4])
00f5f2b8 7ca13714 00000082 00000000 00000104 SHELL32!CCtrlExtIconBase::_GetIconLocationW+0x7b (FPO: [5,0,0])
00f5f2d4 7ca1d306 000a25ac 00000082 00f5f570 SHELL32!CExtractIconBase::GetIconLocation+0x1f (FPO: [6,0,0])
00f5f410 7ca133b6 000dd7e0 00000082 00f5f570 SHELL32!CShellLink::GetIconLocation+0x69 (FPO: [6,68,4])
00f5f77c 7ca03c88 000dd7e0 00000000 0015aa00 SHELL32!_GetILIndexGivenPXIcon+0x9c (FPO: [5,208,4])
00f5f7a4 7ca06693 00131c60 000dd7e0 0015aa00 SHELL32!SHGetIconFromPIDL+0x90 (FPO: [5,0,4])
00f5fe20 7ca12db0 00131c64 0015aa00 00000000 SHELL32!CFSFolder::GetIconOf+0x24e (FPO: [4,405,4])
00f5fe40 7ca15e3c 00131c60 00131c64 0015aa00 SHELL32!SHGetIconFromPIDL+0x20 (FPO: [5,0,0])
00f5fe68 7ca03275 000f8090 0014d5b0 0014a910 SHELL32!CGetIconTask::RunInitRT+0x47 (FPO: [1,2,4])
00f5fe84 75f11b9a 000f8090 75f11b18 75f10000 SHELL32!CRunnableTask::Run+0x54 (FPO: [1,1,4])
00f5fee0 77f49598 00155658 000cb748 77f4957b BROWSEUI!CShellTaskScheduler_ThreadProc+0x111 (FPO: [1,17,0])
00f5fef8 7c937ac2 000cb748 7c98e440 0014cfe0 SHLWAPI!ExecuteWorkItem+0x1d (FPO: [1,0,4])
00f5ff40 7c937b03 77f4957b 000cb748 00000000 ntdll!RtlpWorkerCallout+0x70 (FPO: [Non-Fpo])
00f5ff60 7c937bc5 00000000 000cb748 0014cfe0 ntdll!RtlpExecuteWorkerRequest+0x1a (FPO: [3,0,0])
00f5ff74 7c937b9c 7c937ae9 00000000 000cb748 ntdll!RtlpApcCallout+0x11 (FPO: [4,0,0])
00f5ffb4 7c80b729 00000000 00edfce4 00edfce8 ntdll!RtlpWorkerThread+0x87 (FPO: [1,7,0])
00f5ffec 00000000 7c920250 00000000 00000000 kernel32!BaseThreadStart+0x37 (FPO: [Non-Fpo])


Src here!

:hat:
Temp...
Avatar de l’utilisateur
x[@♥]
 
Messages: 851
Inscription: Lun 21 Sep 2009 15:21
Localisation: Sur la root

Re: Experts Warn of New Windows Shortcut Flaw

Nouveau messagede x[@♥] » Jeu 22 Juil 2010 12:13

Une méthode (temporaire?) venant de Krosoft pour fixer le bug (désactiver les shortcut :roll: ) :

Microsoft has released a stopgap fix to help Windows users protect themselves against threats that may try to target a newly discovered, critical security hole that is present in every supported version of Windows.

Last week, KrebsOnSecurity.com reported that security researchers in Belarus had found a sophisticated strain of malware that was exploiting a previously unknown flaw in the way Windows handles shortcut files. Experts determined that the malware exploiting the vulnerability was being used to attack computers that interact with networks responsible for controlling the operations of large, distributed and very sensitive systems, such as manufacturing and power plants.

When Microsoft initially released an advisory acknowledging the security hole last week, it said customers could disable the vulnerable component by editing the Windows registry. Trouble is, editing the registry can be a dicey affair for those less experienced working under the hood in Windows because one errant change can cause system-wide problems.

But in an updated advisory posted Tuesday evening, Microsoft added instructions for using a much simpler, point-and-click “FixIt” tool to disable the flawed Windows features. That tool, available from this link, allows Windows users to nix the vulnerable component by clicking the “FixIt” icon, following the prompts, and then rebooting the system.

Be advised, however, that making this change could make it significantly more difficult for regular users to navigate their computer and desktop, as it removes the graphical representation of icons on the Task bar and Start menu bar and replaces them with plain, white icons.

For instance, most Windows users are familiar with these icons:

Image

According to Microsoft, after applying this fix, those icons will be replaced with nondescript (and frankly ugly) placeholders that look like this:

Image

There are currently no signs that this vulnerability is being used in anything but targeted attacks against some very important targets. That said, the situation could change rapidly soon. For one thing, a proof-of-concept exploit is now publicly available and embedded into open-source attack tools. And while initial reports suggested the primary means of exploiting this flaw required someone to introduce a strange USB device into their system, experts have since shown that the exploit can also be used to spread and launch malicious programs over network shares.

The SANS Internet Storm Center on Monday made the relatively rare decision to change its threat warning level to yellow over this vulnerability, warning that “wide-scale exploitation is only a matter of time.”

“The proof-of-concept exploit is publicly available, and the issue is not easy to fix until Microsoft issues a patch,” SANS incident handler Lenny Zeltser wrote. “Furthermore, anti-virus tools’ ability to detect generic versions of the exploit have not been very effective so far.”

Both of these potential exploit paths probably make this vulnerability far more dangerous for corporate and business users than for home users. That said, having ugly Start Menu and Taskbar icons for a few weeks until Microsoft issues a real fix for this flaw may be a small price to pay for peace of mind. Also, the FixIt changes can be undone simply by visiting this link and clicking the FixIt icon under the “Disable This Workaround” heading.


Src here!

:hat:
Temp...
Avatar de l’utilisateur
x[@♥]
 
Messages: 851
Inscription: Lun 21 Sep 2009 15:21
Localisation: Sur la root


Retourner vers Discussions



Qui est en ligne

Utilisateurs parcourant ce forum: Aucun utilisateur enregistré et 0 invités

cron