CVE-2020-16160

HIGHNVD 7.57.5
EchelonGraph scoreLOW confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: nvd
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 7.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

GoPro gpmf-parser 1.5 has a division-by-zero vulnerability in GPMF_Decompress(). Parsing malicious input can result in a crash.

CVSS v3
7.5
EG Score
7.5(low)
EPSS
66.9%
KEV
Not listed

Published

October 19, 2020

Last Modified

November 21, 2024

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Frequently asked(5)

What is CVE-2020-16160?
CVE-2020-16160 is a high vulnerability published on October 19, 2020. GoPro gpmf-parser 1.5 has a division-by-zero vulnerability in GPMF_Decompress(). Parsing malicious input can result in a crash.
When was CVE-2020-16160 disclosed?
CVE-2020-16160 was first published in the National Vulnerability Database on October 19, 2020, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2020-16160 actively exploited?
CVE-2020-16160 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 66.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2020-16160?
CVE-2020-16160 has a CVSS v3 base score of 7.5 (NVD). The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2020-16160?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2020-16160, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2020-16160

Explore →

Is Your Infrastructure Affected by CVE-2020-16160?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.