[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BLU169-W81DF5A6EEFA54DF565572BC45B0@phx.gbl>
Date: Mon, 12 Aug 2013 13:31:50 +0000
From: yuange <yuange1975@...mail.com>
To: full-disclosure <full-disclosure@...ts.grok.org.uk>
Subject: Re: 0day IE9/10 information disclosure
vulnerability
somebody's poc
http://weibo.com/p/1005051838905715/weibo?from=page_100505_home&wvr=5.1&mod=weibomore#3610572387549394
微软呀,要怎么说你们呢。3个月的沟通不承认,一定要POC才承认,这么简单的代码看不懂吗?说得那么明白写POC真的有那么难吗?实在太磨叽了。
这个漏洞你们还感谢360吗?不是我不配合,3个月的沟通,不给POC就关闭这个漏洞的修补。顺便问一声,那几个漏洞修补还要花几个月呀?
From: yuange1975@...mail.com
To: full-disclosure@...ts.grok.org.uk
Subject: 0day IE9/10 information disclosure vulnerability
Date: Mon, 29 Jul 2013 07:22:18 +0000
#0day IE9/10 information disclosure vulnerability http://t.cn/zQJYHgA .Technical challenge how to write exploit code?
漏洞报告已经说得很明白,指出问题代码,怎么定位代码。鉴于微软一次次的纠缠于需要提供POC,那就让大家来写POC吧,写好记得发一份给微软。 :)
https://twitter.com/yuange75 我的观点:
#antiNSA 现在APT的大环境下,POC代码、EXP利用技术都是宝贵资源,不想因为中间环节被控制或者SNIFFER而丢失这些宝贵资源,现在坚定报告漏洞不提供POC和EXP,除非有偿的漏洞报告。反汇编指出问题代码点,对于漏洞修补已经提供了足够的重要信息了,要想POC自己分析。
Content of type "text/html" skipped
_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/
Powered by blists - more mailing lists