CVE-2020-36254: scp.c in Dropbear before 2020.79 mishandles the filename of
CVE-2020-36254 is a high-severity flaw (CVSS 8.1) affecting dropbear ssh. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
scp.c in Dropbear before 2020.79 mishandles the filename of . or an empty filename, a related issue to CVE-2018-20685.
Why this priority
- High severity
- Remotely exploitable, no login, no user action
A fixed release or distro patch exists.
Risk facts
| CVSS score | 8.1 (High) |
| Attack vector | Network (remote) |
| Attack complexity | High |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 1.9% (top 21%) |
| CISA exploited list | No |
| Published | 2021-02-25 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2020-36254?
dropbear ssh: upgrade to 2020.79. Exact commands for each OS are on this page.
Is CVE-2020-36254 being exploited?
CVE-2020-36254 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2020-36254 affect?
CVE-2020-36254 affects dropbear ssh. Severity is high (CVSS 8.1). scp.c in Dropbear before 2020.79 mishandles the filename of . or an empty filename, a related issue to CVE-2018-20685.
How urgent is CVE-2020-36254?
Priority 53/100. High severity; Remotely exploitable, no login, no user action
Related CVEs
- CVE-2021-36369 HIGH 7.5 UPGRADE MITIGATE An issue was discovered in Dropbear through 2020.81
- CVE-2019-12953 MEDIUM 5.3 UPGRADE Dropbear 2011.54 through 2018.76 has an inconsistent failure delay that may lead to revealing valid usernames,