CVE-2020-28476: Rejected CVE Entry (Duplicate)

CVE-2020-28476 Overview

CVE-2020-28476 is a rejected CVE candidate that should not be used. This CVE number was assigned as a reservation duplicate of CVE-2021-23336 and has been officially withdrawn from the CVE database.

Critical Impact

This CVE entry has been rejected. All users should reference CVE-2021-23336 instead of this candidate. All references and descriptions have been removed to prevent accidental usage.

Affected Products

• No affected products listed - this is a rejected CVE candidate
• Users should consult CVE-2021-23336 for actual affected product information

Discovery Timeline

• 2021-01-18 - CVE-2020-28476 published to NVD
• 2023-11-07 - Last updated in NVD database with rejection status

Technical Details for CVE-2020-28476

Vulnerability Analysis

This CVE entry has been rejected and contains no valid vulnerability information. The rejection reason indicates this was a duplicate reservation of CVE-2021-23336. When duplicate CVE assignments occur, one entry is rejected to maintain a single authoritative reference for each unique vulnerability.

Organizations maintaining vulnerability databases and security tooling should ensure they do not track or report on this CVE. Any historical references to CVE-2020-28476 in security advisories, vulnerability scanners, or compliance reports should be updated to reference CVE-2021-23336 instead.

Root Cause

This CVE was rejected due to being a reservation duplicate. During the CVE assignment process, the same vulnerability may inadvertently receive multiple candidate numbers. When this occurs, one number is designated as the authoritative identifier while the duplicate is rejected with a reference to the correct CVE.

Attack Vector

No attack vector is applicable to this rejected CVE candidate. For actual vulnerability details, security teams should reference CVE-2021-23336, which contains the complete technical information including attack vectors, affected products, and remediation guidance.

Detection Methods for CVE-2020-28476

Indicators of Compromise

• No IOCs exist for this rejected CVE candidate
• Any existing IOCs associated with this CVE should be remapped to CVE-2021-23336
• Security tools flagging this CVE should be updated to use the correct identifier

Detection Strategies

• Audit vulnerability management databases to replace any references to CVE-2020-28476 with CVE-2021-23336
• Review security scanner configurations to ensure deprecated CVE mappings are updated
• Check SIEM correlation rules for incorrect CVE references

Monitoring Recommendations

• No active monitoring is required for this rejected CVE
• Implement CVE-2021-23336 detection rules where appropriate
• Periodically review vulnerability feeds for CVE status changes and rejections

How to Mitigate CVE-2020-28476

Immediate Actions Required

• Replace all references to CVE-2020-28476 with CVE-2021-23336 in vulnerability tracking systems
• Update any security documentation or compliance reports that reference this CVE
• Review CVE-2021-23336 for actual remediation guidance and patch information

Patch Information

No patch information exists for this rejected CVE candidate. Security teams should consult the CVE-2021-23336 entry for relevant patch and update information regarding the actual vulnerability.

Workarounds

• No workarounds are applicable to this rejected CVE
• Consult CVE-2021-23336 documentation for any available workarounds related to the underlying vulnerability
• Update vulnerability management workflows to handle CVE rejections and duplicates appropriately