CVE-2017-2001
Unknown
Last modified
CVE-2017-2001 is a vulnerability of currently unknown severity. Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none.
Description
Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was in a CNA pool that was not assigned to any issues during 2017. Notes: none
Timeline
- Published
- Last Modified
- Status
- Rejected
Frequently Asked Questions
What is CVE-2017-2001?
Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was in a CNA pool that was not assigned to any issues during 2017. Notes: none
How severe is CVE-2017-2001?
Severity scoring for CVE-2017-2001 is pending analysis.
How do I fix CVE-2017-2001?
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-20003Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultID…
- CVE-2017-20004In the standard library in Rust before 1.19.0, there is a sy…5.9
- CVE-2017-20005NGINX before 1.13.6 has a buffer overflow for years that exc…9.8
- CVE-2017-20006UnRAR 5.6.1.2 and 5.6.1.3 has a heap-based buffer overflow i…7.8
- CVE-2017-20007Ingeteam INGEPAC DA AU AUC_1.13.0.28 (and before) web applic…5.3
- CVE-2017-20008The myCred WordPress plugin before 1.7.8 does not sanitise a…6.1
- CVE-2017-20011A vulnerability was found in WEKA INTEREST Security Scanner …5.5
- CVE-2017-20012A vulnerability classified as problematic has been found in …5.5
- CVE-2017-20013A vulnerability classified as problematic was found in WEKA …5.5
- CVE-2017-20014A vulnerability, which was classified as problematic, has be…5.5
- CVE-2017-20015A vulnerability, which was classified as problematic, was fo…5.5
- CVE-2017-20016A vulnerability has been found in WEKA INTEREST Security Sca…7.5
Are you affected by CVE-2017-2001?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
