Releasing vulnerability advisories is an all-time discussed problem with many different attitudes. Every policy has its own advantages and disadvantages, but I really like CERT’s 45-day policy. So I have adopted their policy with some small changes and use it for my own disclosure processes.
Unfortunately MITRE have changed their CVE assignment process dramatically recently, resulting in less-known applications not being assigned with CVEs anymore. I think that is an inappropriate move, which forces me to use alternatives. Therefore every new disclosure will contain an identifier like RCESEC-YEAR-NUMBER, plus a CVE (in case one is assigned).
In this phase the vendor will be initially notified about the discovery on different ways including a preset public disclosure date. The notification might already include the vulnerability details, which however depends on the contact possibilities offered initially. It does usually also include an initial deadline, which is set 14 days after the time of the first notification. During this 14 days the vendor will be contacted multiple times on multiple ways to make sure the notification is received.
- 14-Days initial deadline ends: The vendor does not respond to any of the initial notifications.
- 45-Days final deadline ends: The vendor does not meet the final disclosure date without an extension.
- An official update is released by the vendor.
- A third party publishes an advisory on the same issue.
- The vendor hasn’t responded to multiple, previous coordination attempts.