|
|
|
On the failings of Pwn2Own 2012 |
Si vous voulez bloquer ce service sur vos fils RSS
Si vous voulez nous contacter ou nous proposer un fil RSS
Menu > Articles de la revue de presse : - l'ensemble [ tous | francophone] - par mots clé [ tous] - par site [ tous] - le tagwall [ voir] - Top bi-hebdo de la revue de presse [ Voir]
On the failings of Pwn2Own 2012 Par SecurityLe [2012-03-30] à 10:04:28
Présentation : This year's Pwn2Own and Pwnium contests were interesting for many reasons. If you look at the results closely, there are many interesting observations and conclusions to be made. 60k is more than enough to encourage disclosure of full exploits As evidenced by the Pwnium results, 60k is certainly enough to motivate researchers into disclosing full exploits, including sandbox escapes or bypasses. There was some minor controversy on this point leading up to the competitions, culminating in this post from ZDI. The post unfortunately was a little strong in its statements including In fact, we don't believe that even the entirety of the 105,000 we are offering would be considered an acceptable bounty , for the 60,000 they are offering, it is incredibly unlikely that anyone will participate and such an exploit against Chrome will never see the light of day at CanSecWest . At least we all now have data I don't expect ZDI to make this mistake again. Without data, it's an understandable mistake to have made. Bad actors will find loopholes and punk you One of the stated -- and laudable -- goals of both Pwn2Own and Pwnium is to make users safer by getting bugs fixed. As recently noted by the EFF, there are some who are not interested in getting bugs fixed. At face value, it would seem to be counterproductive for these greyhat or blackhat parties to participate. Enter VUPEN, who somehow managed to turn up and get the best of all worlds 60k, tons of free publicity for their dubious business model and... minimal cost. To explore the minimal cost, let's look at one of the bugs they used a Flash bug not Chrome as widely reported , present in Flash 11.1 but already fixed in Flash 11.2. In other words, the bug they used already had a fixed lifetime. Using such a bug enabled them to collect a large prize whilst only handing over a doomed asset in return. Although operating within the rules, their entry did not do much to advance user security and safety -- the bug fix was already in the pipeline to users. They did however punk 60k out of Pwn2Own and turned the whole contest into a VUPEN marketing spree. Game theory At the last minute at Pwn2Own, contestants Vincenzo and Willem swooped in with a Firefox exploit to collect a 30k second place prize. The timing suggests that they were waiting to see if their single 0-day would net them a prize or not. It did. We'll never know what they would have done if the 30k reward was already sewn up by someone else, but one possibility is a non-disclosure -- which wouldn't help make anyone safer. Fixing future contests The data collected suggests some possible structure to future contests to ensure they bring maximal benefit to user safety Require full exploits, including sandbox escapes or bypasses. Do not pay out for bugs already fixed in development releases or repositories. Have a fixed reward value per exploit.
Les mots clés de la revue de presse pour cet article : pwn2own
Les derniers articles du site "Security" :
- Exploiting 64-bit Linux like a boss
- The joys and hazards of multi-process browser security
- Chrome 20 on Linux and Flash sandboxing
- vsftpd-3.0.0 and seccomp filter sandboxing is here
- vsftpd-3.0.0-pre2
- On the failings of Pwn2Own 2012
Menu > Articles de la revue de presse : - l'ensemble [ tous | francophone] - par mots clé [ tous] - par site [ tous] - le tagwall [ voir] - Top bi-hebdo de la revue de presse [ Voir]
Si vous voulez bloquer ce service sur vos fils RSS :
- avec iptables "iptables -A INPUT -s 88.190.17.190 --dport 80 -j DROP"
- avec ipfw et wipfw "ipfw add deny from 88.190.17.190 to any 80"
- Nous contacter par mail
| Mini-Tagwall des articles publiés sur SecuObs : | | | | sécurité, exploit, windows, outil, attaque, réseau, microsoft, metasploit, audit, vulnérabilité, système, virus, internet, usbsploit, données, protocol, présentation, linux, source, réseaux, bluetooth, scanner, reverse, conférence, shell, meterpreter, vista, rootkit, engineering, mobile, security, wishmaster, malicieux, https, trames, paquet, noyau, téléphone, détection, botnet, forensic, libre, snort, utilisant, sysun |
| Mini-Tagwall de l'annuaire video : | | | | curit, security, biomet, metasploit, biometric, cking, password, windows, botnet, defcon, tutorial, crypt, xploit, exploit, lockpicking, linux, attack, wireshark, vmware, rootkit, conference, network, shmoocon, backtrack, virus, conficker, elcom, etter, elcomsoft, server, meterpreter, openvpn, ettercap, openbs, iphone, shell, openbsd, iptables, securitytube, deepsec, source, office, systm, openssh, radio |
| Mini-Tagwall des articles de la revue de presse : | | | | security, microsoft, windows, hacker, attack, network, vulnerability, google, exploit, malware, internet, remote, iphone, server, inject, patch, apple, twitter, mobile, virus, ebook, facebook, vulnérabilité, crypt, source, linux, password, intel, research, virtual, phish, access, tutorial, trojan, social, privacy, firefox, adobe, overflow, office, cisco, conficker, botnet, pirate, sécurité |
| Mini-Tagwall des Tweets de la revue Twitter : | | | | security, linux, botnet, attack, metasploit, cisco, defcon, phish, exploit, google, inject, server, firewall, network, twitter, vmware, windows, microsoft, compliance, vulnerability, python, engineering, source, kernel, crypt, social, overflow, nessus, crack, hacker, virus, iphone, patch, virtual, javascript, malware, conficker, pentest, research, email, password, adobe, apache, proxy, backtrack |
|
|
|
|
|
