CVE-2020-37021
Local privilege escalation in 10-Strike Bandwidth Monitor 3.9 via unquoted service path
Is CVE-2020-37021 being exploited?
Not confirmed. CVE-2020-37021 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.12% probability of exploitation in the next 30 days.
How severe is CVE-2020-37021?
CVE-2020-37021 is rated High with a CVSS score of 8.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2020-37021?
Not known from our data. No patch reference has been recorded for CVE-2020-37021, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2020-37021 affect?
CVE-2020-37021 affects 10-Strike Bandwidth Monitor 3.9. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2020-37021?
Patch/upgrade when available; verify service paths are quoted
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Local attacker can escalate to SYSTEM by placing a malicious executable in an unquoted service path during startup.
Patch when possible
- affected3.9
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.