I was unsure if this file (CVE-2019-15666) was complete because of the large amount of incomplete information. First, it is important to fill out the section relating to the dates. At least one date should be included.
There is little information about the vulnerability in the description and almost every other explanatory section has less than ten words.
Lastly, I can't tell if the VCC section is linking to refactoring or vulnerability-introducing commits.
Overall, I think this CVE just needs more information.
Upvotes
CVE-2019-15666 receives a 2/10 upvote score due to the minimal information within the review, making it difficult to understand the vulnerability and its impact.
Reviewed file: https://github.com/VulnerabilityHistoryProject/vulnerabilities/blob/dcae4786adb246e30d2f0cb742faa0297cb24092/cves/kernel/CVE-2019-15666.yml
I was unsure if this file (CVE-2019-15666) was complete because of the large amount of incomplete information. First, it is important to fill out the section relating to the dates. At least one date should be included.
There is little information about the vulnerability in the description and almost every other explanatory section has less than ten words.
Lastly, I can't tell if the VCC section is linking to refactoring or vulnerability-introducing commits.
Overall, I think this CVE just needs more information.
Upvotes CVE-2019-15666 receives a 2/10 upvote score due to the minimal information within the review, making it difficult to understand the vulnerability and its impact.