LiveActive security incident?Get immediate response
CVE Record

CVE-2020-36254: scp.c in Dropbear before 2020.79 mishandles the filename of .

scp.c in Dropbear before 2020.79 mishandles the filename of . or an empty filename, a related issue to CVE-2018-20685.

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2020-36254 affects Dropbear before 2020.79. The issue is in scp filename handling for a dot or empty filename. The public record rates it high because successful exploitation could affect confidentiality, integrity, and availability, but the CVSS vector also says attack complexity is high.

Executive priority

Prioritize remediation in exposed environments because the potential impact is broad, but urgency is tempered by high attack complexity and no supplied evidence of active exploitation.

Technical view

Dropbear scp.c mishandles special filename cases involving "." or an empty filename, related to CVE-2018-20685. The CVSS 3.1 vector is AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H. The supplied data identifies Dropbear before 2020.79 and references an upstream commit.

Likely exposure

Exposure is likely limited to systems that include Dropbear before 2020.79 and use or expose its scp functionality. The affected-product metadata in the source bundle is incomplete, so teams should verify packaged and bundled Dropbear versions directly.

Exploitation context

The source bundle does not show CISA KEV listing or other evidence of active exploitation. Treat this as a high-impact vulnerability with high attack complexity, not as a confirmed exploited-in-the-wild issue.

Researcher notes

Evidence is sparse: the affected vendor/product fields are n/a, and the primary technical reference is an upstream commit. Avoid assuming affected downstream products without version confirmation. The CVSS vector supports remote, unauthenticated, no-user-interaction assessment but high complexity.

Mitigation direction

  • Upgrade Dropbear to 2020.79 or later where applicable.
  • Check OS, appliance, and firmware vendor advisories for patched Dropbear builds.
  • Disable unnecessary scp exposure where operationally feasible.
  • Prioritize externally reachable or untrusted-access Dropbear deployments.

Validation and detection

  • Inventory systems and software bundles for Dropbear versions before 2020.79.
  • Confirm whether Dropbear scp functionality is installed, enabled, or reachable.
  • Verify vendor package versions include the upstream fix or equivalent backport.
  • Review change records against the referenced Dropbear commit.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2020-36254 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.1CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H2.25.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.1High
CVSS 3.1 vector shape for CVE-2020-36254Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.