CVE-2017-2002
Unknown
Last modified
CVE-2017-2002 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-2002?
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-2002?
Severity scoring for CVE-2017-2002 is pending analysis.
How do I fix CVE-2017-2002?
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-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
- CVE-2017-20017A vulnerability, which was classified as critical, has been …8.8
- CVE-2017-20018A vulnerability was found in XAMPP 7.1.1-0-VC14. It has been…7.8
- CVE-2017-20019A vulnerability classified as problematic was found in Solar…7.5
- CVE-2017-20020A vulnerability, which was classified as problematic, has be…8.8
- CVE-2017-20021A vulnerability, which was classified as critical, was found…9.8
- CVE-2017-20022A vulnerability has been found in Solare Solar-Log 2.8.4-56/…7.5
- CVE-2017-20023A vulnerability was found in Solare Solar-Log 2.8.4-56/3.5.2…9.8
- CVE-2017-20024A vulnerability was found in Solare Solar-Log 2.8.4-56/3.5.2…7.5
- CVE-2017-20025A vulnerability was found in Solare Solar-Log 2.8.4-56/3.5.2…9.8
Are you affected by CVE-2017-2002?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST