cve.bz

CVE-2020-15778 OS Command Injection

7.4 highExploit referenceEPSS 14%

High (7.4). EPSS 14% estimated probability of exploitation activity in the next 30 days.

On this page
scp in OpenSSH through 8.3p1 allows command injection in the scp.c toremote function, as demonstrated by backtick characters in the destination argument. NOTE: the vendor reportedly has stated that they intentionally omit validation of "anomalous argument transfers" because that could "stand a great chance of breaking existing workflows."

Severity

CVSS 3.1

7.4 high
CVSS:3.1/AV:A/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
EPSS
14% (unchanged from 14% a week ago; 14% 30 days ago) estimated probability of exploitation activity in the next 30 days; 97th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: total, assessed 2024-05-01. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-78 Improper Neutralization of Special Elements used in an OS Command (OS Command Injection)
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2020-15778 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2020-15778?via=ask-ai-copy and https://cve.bz/cve/CVE-2020-15778?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2020-15778 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2020-15778

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2020-15778](https://cve.bz/cve/badge/CVE-2020-15778.svg)](https://cve.bz/cve/CVE-2020-15778)

HTML:

<a href="https://cve.bz/cve/CVE-2020-15778"><img src="https://cve.bz/cve/badge/CVE-2020-15778.svg" alt="CVE-2020-15778"></a>

Affected

Versions

From the NVD's CPE matches.

ProductAffected
openbsd:opensshbefore 8.3
openbsd:openssh8.3
openbsd:openssh8.3:p1
netapp:active_iq_unified_manager9.5 and later

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14opensshno fix listedDEBIAN-CVE-2020-15778
Ubuntu18.04:LTS, 20.04:LTSopenssh-ssh1no fix listedUBUNTU-CVE-2020-15778
UbuntuPro:14.04:LTS, Pro:16.04:LTS, Pro:18.04:LTS and 1 moreopensshno fix listedUBUNTU-CVE-2020-15778
Red Hatenterprise_linux:8::appstreamopenssh-askpass, openssh-debuginfo, openssh-debugsource and 6 more0:8.0p1-24.el8RHSA-2024:3166
Red Hatenterprise_linux:8::appstreampam_ssh_agent_auth-debuginfo0:0.10.3-7.24.el8RHSA-2024:3166
Red Hatenterprise_linux:8::baseosopenssh, openssh-cavs, openssh-ldap and 11 more0:8.0p1-24.el8RHSA-2024:3166
Red Hatenterprise_linux:8::baseospam_ssh_agent_auth, pam_ssh_agent_auth-debuginfo0:0.10.3-7.24.el8RHSA-2024:3166
AlmaLinux8openssh, openssh-cavs, openssh-ldap and 4 more8.0p1-24.el8ALSA-2024:3166
AlmaLinux8pam_ssh_agent_auth0.10.3-7.24.el8ALSA-2024:3166
Rocky Linux8openssh0:8.0p1-24.el8RLSA-2024:3166
Alpinev3.19, v3.20, v3.21 and 3 moreopenssh8.3_p1-r0ALPINE-CVE-2020-15778

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; AlmaLinux's OSV database, MIT; Rocky Linux's errata, BSD-3-Clause; the Alpine secdb, CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · Alpine.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This security flaw lies in the way scp command parses its command line arguments. The SSH protocol or any other applications shipped as a part of openssh-clients packages are not vulnerable.

In order to exploit this flaw, the attacker needs to social engineer or manipulate a system administrator (who has root access on the remote server) to run scp with a malicious command line parameter.

Administrators can uninstall openssh-clients for additional protection against accidental usage of this binary. Removing the openssh-clients package will make binaries like scp and ssh etc unavailable on that system. Also administrators can change the execute permissions on the scp binary. However this mitigation will be in place until the openssh-clients package is updated.

The loss of confidentiality, integrity and availability would depend on the system umask and selinux policies. For example, if the system umask is 000, one user CAN get access to another user's files and even execute them. However default umask for pretty much any modern unix system is 033, which gives a default permisson of 744. This does not cause any confidentiality problems that already does not exist outside of the scope of this bug. Also since the default permissions based on the umask would guard write and execute, there is no way to cause any loss of Integrity or Availability.

Red Hat's mitigation

As per upstream, because of the way scp is based on a historical protocol called rcp which relies on that style of argument passing and therefore encounters expansion problems. Making changes to how the scp command line works breaks the pattern used by scp consumers. Upstream therefore recommends the use of rsync in place of scp for better security.

Also, adding to the mitigation strategy the SCP protocol can be disabled by following the steps in the following documentation:

https://access.redhat.com/node/7053909

More details about supported alternatives available at: https://access.redhat.com/articles/5284081

ProductPackageStateAdvisory
Red Hat Enterprise Linux 8openssh-0:8.0p1-24.el8Fixed 2024-05-22RHSA-2024:3166
Red Hat Enterprise Linux 5opensshOut of support scope
Red Hat Enterprise Linux 6opensshOut of support scope
Red Hat Enterprise Linux 7opensshWill not fix

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2020-15778.

ICS advisories (CISA)

AdvisoryTitlePublishedSectorsAffectedFixed
ICSA-23-348-10Siemens SIMATIC S7-15002023-12-12Critical Manufacturing, Transportation Systems, Energy, Healthcare and Public Health, Financial Services, Government Services and FacilitiesSIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AB0), SIMATIC S7-1500 CPU 1518-4 PN/DP MFP (6ES7518-4AX00-1AC0), SIMATIC S7-1500 CPU 1518F-4 PN/DP MFP (6ES7518-4FX00-1AB0) and 2 morenone listed

From CISA's ICS advisories (CSAF), provided under CISA's notification. Only the facts are shown; each advisory is on CISA's page. Credits.

Attack patterns (CAPEC)

  • CAPEC-6 Argument Injection Likelihood: High · Severity: High
  • CAPEC-15 Command Delimiters Likelihood: High · Severity: High
  • CAPEC-43 Exploiting Multiple Input Interpretation Layers Likelihood: Medium · Severity: High
  • CAPEC-88 OS Command Injection Likelihood: High · Severity: High
  • CAPEC-108 Command Line Execution through SQL Injection Likelihood: Low · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON