@attritionorg @SushiDude Indeed, but that's when the Y2K effect hits :)
-
-
Replying to @wireghoul
.
@wireghoul@attritionorg if/when CVE-10K hits it will be too late for some. Planning important now http://cve.mitre.org/cve/identifiers/syntaxchange.html …1 reply 0 retweets 0 likes -
Replying to @SushiDude
@SushiDude@wireghoul we haven't updated for 5 digits yet (minor change). i think if CVE hits 5 digits this year, it will be forced.1 reply 0 retweets 0 likes -
Replying to @attritionorg
.
@attritionorg current pace is 9453 by Dec 31 - too close 4 comfort, + plus IDs don't stop in 2015#didCVEbreak10Kyet@wireghoul5 replies 1 retweet 0 likes -
Replying to @SushiDude
@SushiDude@attritionorg@wireghoul I need to find 547 tmp vulns then, how are we scoring http://github.org projects for CVE again? =)1 reply 0 retweets 0 likes -
Replying to @kurtseifried
@kurtseifried@SushiDude@wireghoul you can race codevigilant's WP plugin XSS marathon for numbers1 reply 0 retweets 0 likes -
Replying to @attritionorg
@attritionorg@kurtseifried@wireghoul codevigilant was a large-scale experiment with, shall we say, mixed results. Might not repeat4 replies 0 retweets 0 likes -
Replying to @SushiDude
@SushiDude@attritionorg@kurtseifried@wireghoul If i may say so@CodeVigilant second lot will be out soon with another 100+ issues.1 reply 0 retweets 0 likes -
Replying to @anantshri
@anantshri@SushiDude@kurtseifried@wireghoul@CodeVigilant if you have influence, can future advisories indicate stored vs reflected?3 replies 0 retweets 0 likes -
Replying to @attritionorg
@attritionorg@anantshri@SushiDude@wireghoul@CodeVigilant REd Hat Bugzilla has details like that, beyond that I have no control1 reply 0 retweets 0 likes
@kurtseifried that was directed to the CodeVigilant side.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.