| CVE | Vendors | Products | Updated | CVSS v3.1 | 
        | 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 | 
    
    
    
        | 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-1218.  Reason: This candidate is a duplicate of CVE-2005-1218.  Notes: All CVE users should reference CVE-2005-1218 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-1915.  Reason: This candidate is a duplicate of CVE-2005-1915.  Notes: All CVE users should reference CVE-2005-1915 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-1921.  Reason: This candidate is a duplicate of CVE-2005-1921.  Notes: All CVE users should reference CVE-2005-1921 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-1855.  Reason: This candidate is a duplicate of CVE-2005-1855.  Notes: All CVE users should reference CVE-2005-1855 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-1250.  Reason: This candidate is a duplicate of CVE-2005-1250.  Notes: this duplicate occurred as a result of multiple independent discoveries and insufficient coordination by the vendor and CNA.  All CVE users should reference CVE-2005-1250 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-1841.  Reason: This candidate is a duplicate of CVE-2005-1841.  Notes: this duplicate occurred as a result of separate assignments by multiple CNAs, one to the researcher and one to the vendor.  All CVE users should reference CVE-2005-1841 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: 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: none. Reason: The CNA or individual who requested this candidate did not associate it with any vulnerability during 2005. Notes: none |