CVE-2017-2605
Unknown
Last modified
CVE-2017-2605 is a vulnerability of currently unknown severity. Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2017-1000362.
Description
Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2017-1000362. Reason: This candidate is a duplicate of CVE-2017-1000362. A vendor reference identifier was mistakenly treated as a CVE ID. Notes: All CVE users should reference CVE-2017-1000362 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage
Timeline
- Published
- Last Modified
- Status
- Rejected
Frequently Asked Questions
What is CVE-2017-2605?
Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2017-1000362. Reason: This candidate is a duplicate of CVE-2017-1000362. A vendor reference identifier was mistakenly treated as a CVE ID. Notes: All CVE users should reference CVE-2017-1000362 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage
How severe is CVE-2017-2605?
Severity scoring for CVE-2017-2605 is pending analysis.
How do I fix CVE-2017-2605?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2017
- CVE-2017-2599Jenkins before versions 2.44 and 2.32.2 is vulnerable to an …5.4
- CVE-2017-2600In jenkins before versions 2.44, 2.32.2 node monitor data co…4.3
- CVE-2017-2601Jenkins before versions 2.44, 2.32.2 is vulnerable to a pers…5.4
- CVE-2017-2602jenkins before versions 2.44, 2.32.2 is vulnerable to an imp…3.1
- CVE-2017-2603Jenkins before versions 2.44, 2.32.2 is vulnerable to a user…2.6
- CVE-2017-2604In Jenkins before versions 2.44, 2.32.2 low privilege users …4.3
- CVE-2017-2606Jenkins before versions 2.44, 2.32.2 is vulnerable to an inf…4.3
- CVE-2017-2607jenkins before versions 2.44, 2.32.2 is vulnerable to a pers…4.2
- CVE-2017-2608Jenkins before versions 2.44, 2.32.2 is vulnerable to a remo…8.8
- CVE-2017-2609jenkins before versions 2.44, 2.32.2 is vulnerable to an inf…4.3
- CVE-2017-2610jenkins before versions 2.44, 2.32.2 is vulnerable to a pers…5.4
- CVE-2017-2611Jenkins before versions 2.44, 2.32.2 is vulnerable to an ins…4.3
Are you affected by CVE-2017-2605?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST