CVE-2020-15311
Unknown
Last modified
This CVE is reserved or rejected; no details have been published by NVD.
Description
Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2008-4080. Reason: This candidate is a duplicate of CVE-2008-4080.2. Notes: All CVE users should reference CVE-2008-4080.2 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage
Timeline
- Published
- Last Modified
- Status
- Rejected
Related CVEs from 2020
- CVE-2020-15305An issue was discovered in OpenEXR before 2.5.2. Invalid inp…5.5
- CVE-2020-15306An issue was discovered in OpenEXR before v2.5.2. Invalid ch…5.5
- CVE-2020-15307Nozomi Guardian before 19.0.4 allows attackers to achieve st…6.1
- CVE-2020-15308Support Incident Tracker (aka SiT! or SiTracker) 3.67 p2 all…7.2
- CVE-2020-15309An issue was discovered in wolfSSL before 4.5.0, when single…7
- CVE-2020-1531An elevation of privilege vulnerability exists when the Wind…7.8
- CVE-2020-15312Zyxel CloudCNM SecuManager 3.1.0 and 3.1.1 has a hardcoded D…5.9
- CVE-2020-15313Zyxel CloudCNM SecuManager 3.1.0 and 3.1.1 has a hardcoded E…5.9
- CVE-2020-15314Zyxel CloudCNM SecuManager 3.1.0 and 3.1.1 has a hardcoded R…5.9
- CVE-2020-15315Zyxel CloudCNM SecuManager 3.1.0 and 3.1.1 has a hardcoded D…5.9
- CVE-2020-15316Zyxel CloudCNM SecuManager 3.1.0 and 3.1.1 has a hardcoded E…5.9
- CVE-2020-15317Zyxel CloudCNM SecuManager 3.1.0 and 3.1.1 has a hardcoded R…5.9
Are you affected by CVE-2020-15311?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST