Is CVE-2017-1000180 being actively exploited?

It is not currently listed in CISA's Known Exploited Vulnerabilities catalog, and no EPSS exploit-prediction score is available yet.

How do I fix CVE-2017-1000180?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2017-1000180 published?

CVE-2017-1000180 was published on 2017-08-20 and last updated on 2023-11-07.

CVE-2017-1000180

CVE-2017-1000180 is a security vulnerability that is still awaiting full analysis and scoring.

Key facts

Actively exploited: Not listed in CISA KEV
Published: 2017-08-20
Last modified: 2023-11-07

Description

Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2017-11100. Reason: This candidate is a reservation duplicate of CVE-2017-11100. Notes: All CVE users should reference CVE-2017-11100 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage

Frequently asked questions

What is CVE-2017-1000180?: Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2017-11100. Reason: This candidate is a reservation duplicate of CVE-2017-11100. Notes: All CVE users should reference CVE-2017-11100 instead of this candidate. All references and descriptions in this candidate have been removed to prevent accidental usage
Is CVE-2017-1000180 being actively exploited?: It is not currently listed in CISA's Known Exploited Vulnerabilities catalog, and no EPSS exploit-prediction score is available yet.
How do I fix CVE-2017-1000180?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2017-1000180 published?: CVE-2017-1000180 was published on 2017-08-20 and last updated on 2023-11-07.