4 ms·
> I'm curious the motivations to release such a serious, and complex, 0day on new years eve!? CVE 2018-0001, it's all about namespaces.
by Godel_unicode 9y ago
> I'm curious the motivations to release such a serious, and complex, 0day on new years eve!?
CVE 2018-0001, it's all about namespaces.
- floatingatoll 9y agoBonus points if they issue it as CVE-2018-65536 (pen-test the world, so to speak) EDIT: "No one would ever store the CVE incrementing fragment as a 16-bit unsigned int!"
- tlrobinson 9y agoCVE 2018-0002: Flaw in CVE numbering procedure incentivizes dropping zero days on New Year’s Eve.
- stevekemp 9y agoI remember waiting to report a security issue with some trivial setuid application until January, back a few years, specifically so I could claim the first CVE of the year. I was unlucky and it didn't work out, but come December time I do wonder if I should dedicate more time to audits ..
- codezero 9y agoLooks like that number was already reserved for a still unpublished vuln. We’re already up to > 3000 in 2018!