LiveActive security incident?Get immediate response
CVE Record

CVE-2018-20685: In OpenSSH 7.9, scp.c in the scp client allows remote SSH servers to bypass intended access restrictions vi...

In OpenSSH 7.9, scp.c in the scp client allows remote SSH servers to bypass intended access restrictions via the filename of . or an empty filename. The impact is modifying the permissions of the target directory on the client side.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This flaw affects the OpenSSH scp client. A malicious or compromised SSH server could abuse unusual filenames to change permissions on the client’s target directory. It is not a remote server takeover, but it can weaken client-side file protections when users or automation pull files with scp.

Executive priority

Treat as a moderate client-side integrity issue. It deserves routine but prompt patching, especially on admin and automation systems. Escalate only if business processes rely on scp downloads from untrusted or customer-controlled servers.

Technical view

CVE-2018-20685 is an OpenSSH 7.9 scp.c authorization/access-control flaw involving a filename of . or an empty filename. The documented impact is client-side target-directory permission modification. The CVSS 3.1 score is 5.3 with network attack vector, high complexity, and required user interaction.

Likely exposure

Exposure is mainly on systems using vulnerable OpenSSH scp clients, especially administrator workstations, build hosts, and scripts that download files from less-trusted SSH servers. The source bundle does not provide a complete affected-product matrix beyond OpenSSH 7.9 and vendor advisories.

Exploitation context

The source bundle does not show KEV listing or active exploitation. Abuse requires the client to connect with scp to a malicious or compromised SSH server. The practical risk is higher where users or automation retrieve files from third-party, shared, or poorly controlled servers.

Researcher notes

Evidence points to a narrow scp client flaw, categorized as CWE-863. The upstream OpenSSH and OpenBSD references provide the code-level fix context. Do not infer broader SSH daemon compromise; the described impact is target-directory permission modification on the client side.

Mitigation direction

  • Apply OpenSSH updates from the operating-system or appliance vendor advisory.
  • Prioritize clients that pull files from external or untrusted SSH servers.
  • Avoid legacy scp downloads from untrusted servers until patched.
  • Check NetApp, Oracle, Siemens, and distribution advisories where relevant.
  • Use vendor guidance rather than assuming one universal fixed version.

Validation and detection

  • Inventory systems using OpenSSH scp clients and record package versions.
  • Compare installed packages against Debian, Ubuntu, Gentoo, Red Hat, and vendor advisories.
  • Review automation that pulls files using scp from remote servers.
  • Confirm patched clients no longer match vulnerable vendor package ranges.
  • Inspect sensitive download directories for unexpected permission weakening.
Prepared
Confidence
high
Sources
12

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.

cwe · medium confidence lookup

CWE-863: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2018-20685 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
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

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

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
14Source 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
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N1.63.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2018-20685Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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

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

CWE-863 · source CWE mapping

Incorrect Authorization

Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.