| CVE | Vendors | Products | Updated | CVSS v3.1 | 
        | DO NOT USE THIS CANDIDATE NUMBER.  ConsultIDs: CVE-2005-3150.  Reason: This candidate was privately assigned by a CNA to an issue, but the issue was published through separate channels and assigned a new identifier by the MITRE CNA, so it is a duplicate of CVE-2005-3150. Notes: All CVE users should reference CVE-2005-3150 instead of this candidate.  All references and descriptions in this candidate have been removed to prevent accidental usage | 
    
    
    
        | DO NOT USE THIS CANDIDATE NUMBER.  ConsultIDs: CVE-2005-2986.  Reason: This candidate is a duplicate of CVE-2005-2986.  Notes: All CVE users should reference CVE-2005-2986 instead of this candidate.  All references and descriptions in this candidate have been removed to prevent accidental usage | 
    
    
    
        | DO NOT USE THIS CANDIDATE NUMBER.  ConsultIDs: CVE-2005-4802, CVE-2005-4803.  Reason: this candidate was intended for one issue, but the description and references inadvertently combined multiple issues. Notes: All CVE users should consult CVE-2005-4802 and CVE-2005-4803 to determine which ID is appropriate.  All references and descriptions in this candidate have been removed to prevent accidental usage | 
    
    
    
        | DO NOT USE THIS CANDIDATE NUMBER.  ConsultIDs: CVE-2005-3663, CVE-2005-3664.  Reason: this candidate was intended for one issue, but multiple advisories used this candidate for different issues.  Notes: All CVE users should consult CVE-2005-3663 and CVE-2005-3664 to determine which ID is appropriate.  All references and descriptions in this candidate have been removed to prevent accidental usage | 
    
    
    
        | DO NOT USE THIS CANDIDATE NUMBER.  ConsultIDs: CVE-2005-2799.  Reason: This candidate is a duplicate of CVE-2005-2799.  Notes: All CVE users should reference CVE-2005-2799 instead of this candidate.  All references and descriptions in this candidate have been removed to prevent accidental usage | 
    
    
    
        | DO NOT USE THIS CANDIDATE NUMBER.  ConsultIDs: CVE-2005-2855.  Reason: This candidate is a duplicate of CVE-2005-2855.  Notes: All CVE users should reference CVE-2005-2855 instead of this candidate.  All references and descriptions in this candidate have been removed to prevent accidental usage | 
    
    
    
        | DO NOT USE THIS CANDIDATE NUMBER.  ConsultIDs: CVE-2005-2872, CVE-2005-2873.  Reason: this candidate's description originally combined two separate issues.  Notes: All CVE users should consult CVE-2005-2872 and CVE-2005-2873 to determine the appropriate identifier for the issue | 
    
    
    
        | DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Notes: none | 
    
    
    
        | DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnerability during 2005. Notes: none | 
    
    
    
        | DO NOT USE THIS CANDIDATE NUMBER.  ConsultIDs: CVE-2005-2041.  Reason: This candidate is a duplicate of CVE-2005-2041.  Notes: All CVE users should reference CVE-2005-2041 instead of this candidate.  All references and descriptions in this candidate have been removed to prevent accidental usage | 
    
    
    
        | DO NOT USE THIS CANDIDATE NUMBER.  ConsultIDs: CVE-2005-2552.  Reason: This candidate is a duplicate of CVE-2005-2552.  Notes: All CVE users should reference CVE-2005-2552 instead of this candidate.  All references and descriptions in this candidate have been removed to prevent accidental usage | 
    
    
    
        | DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnerability during 2005. Notes: none | 
    
    
    
        | DO NOT USE THIS CANDIDATE NUMBER.  ConsultIDs: CVE-2005-2641.  Reason: This candidate is a duplicate of CVE-2005-2641.  Notes: All CVE users should reference CVE-2005-2641 instead of this candidate.  All references and descriptions in this candidate have been removed to prevent accidental usage | 
    
    
    
        | DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was in a CNA pool that was not assigned to any issues during 2005. Notes: none | 
    
    
    
        | DO NOT USE THIS CANDIDATE NUMBER.  ConsultIDs: CVE-2005-2370.  Reason: This candidate is a duplicate of CVE-2005-2370.  Notes: All CVE users should reference CVE-2005-2370 instead of this candidate.  All references and descriptions in this candidate have been removed to prevent accidental usage | 
    
    
    
        | DO NOT USE THIS CANDIDATE NUMBER.  ConsultIDs: CVE-2005-2369.  Reason: This candidate is a duplicate of CVE-2005-2369.  Notes: All CVE users should reference CVE-2005-2369 instead of this candidate.  All references and descriptions in this candidate have been removed to prevent accidental usage | 
    
    
    
        | DO NOT USE THIS CANDIDATE NUMBER.  ConsultIDs: CVE-2005-2403.  Reason: This candidate is a duplicate of CVE-2005-2403.  Notes: All CVE users should reference CVE-2005-2403 instead of this candidate.  All references and descriptions in this candidate have been removed to prevent accidental usage | 
    
    
    
        | DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnerability during 2005. Notes: none | 
    
    
    
        | DO NOT USE THIS CANDIDATE NUMBER.  ConsultIDs: CVE-2005-2335, CVE-2005-2356.  Reason: due to a typo in an advisory, this candidate was accidentally referenced.  Notes: All CVE users should consult CVE-2005-2335 and CVE-2005-2356 to determine the appropriate identifier for the issue | 
    
    
    
        | DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnerability during 2005. Notes: none |