{"api_version":"1","generated_at":"2026-07-23T06:05:44+00:00","cve":"CVE-2005-2355","urls":{"html":"https://cve.report/CVE-2005-2355","api":"https://cve.report/api/cve/CVE-2005-2355.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2005-2355","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2005-2355"},"summary":{"title":"CVE-2005-2355","description":"** REJECT **  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.","state":"REJECT","assigner":"cve@mitre.org","published_at":"2005-07-25 04:00:00","updated_at":"2023-11-07 01:57:00"},"problem_types":[],"metrics":[],"references":[{"url":"http://www.redhat.com/archives/fedora-announce-list/2005-July/msg00104.html","name":"MISC:http://www.redhat.com/archives/fedora-announce-list/2005-July/msg00104.html","refsource":"MITRE","tags":[],"title":"Wrong CVE CAN number in fetchmail update announcements","mime":"text/html","httpstatus":"200","archivestatus":"200"},{"url":"https://www.cve.org/CVERecord?id=CVE-2005-2355","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2005-2355","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"data_type":"CVE","data_format":"MITRE","data_version":"4.0","CVE_data_meta":{"ID":"CVE-2005-2355","ASSIGNER":"cve@mitre.org","STATE":"REJECT"},"description":{"description_data":[{"lang":"eng","value":"** REJECT **  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."}]}},"nvd":{"publishedDate":"2005-07-25 04:00:00","lastModifiedDate":"2023-11-07 01:57:00","problem_types":[],"metrics":[],"configurations":{"CVE_data_version":"4.0","nodes":[]}},"legacy_mitre":{"record":{"CveYear":"2005","CveId":"2355","Ordinal":"12269","Title":"CVE-2005-2355","CVE":"CVE-2005-2355","Year":"2005"},"notes":[{"CveYear":"2005","CveId":"2355","Ordinal":"1","NoteData":"** REJECT **\n\nDO 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.","Type":"Description","Title":null},{"CveYear":"2005","CveId":"2355","Ordinal":"2","NoteData":"2005-07-25","Type":"Other","Title":"Published"},{"CveYear":"2005","CveId":"2355","Ordinal":"3","NoteData":"2005-11-02","Type":"Other","Title":"Modified"}]}}}