CVSS 3.1
7.4 highCVSS:3.1/AV:A/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:HHigh (7.4). EPSS 14% estimated probability of exploitation activity in the next 30 days.
CVSS:3.1/AV:A/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:HExplain 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.
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| openbsd:openssh | before 8.3 |
| openbsd:openssh | 8.3 |
| openbsd:openssh | 8.3:p1 |
| netapp:active_iq_unified_manager | 9.5 and later |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12, 13, 14 | openssh | no fix listed | DEBIAN-CVE-2020-15778 |
| Ubuntu | 18.04:LTS, 20.04:LTS | openssh-ssh1 | no fix listed | UBUNTU-CVE-2020-15778 |
| Ubuntu | Pro:14.04:LTS, Pro:16.04:LTS, Pro:18.04:LTS and 1 more | openssh | no fix listed | UBUNTU-CVE-2020-15778 |
| Red Hat | enterprise_linux:8::appstream | openssh-askpass, openssh-debuginfo, openssh-debugsource and 6 more | 0:8.0p1-24.el8 | RHSA-2024:3166 |
| Red Hat | enterprise_linux:8::appstream | pam_ssh_agent_auth-debuginfo | 0:0.10.3-7.24.el8 | RHSA-2024:3166 |
| Red Hat | enterprise_linux:8::baseos | openssh, openssh-cavs, openssh-ldap and 11 more | 0:8.0p1-24.el8 | RHSA-2024:3166 |
| Red Hat | enterprise_linux:8::baseos | pam_ssh_agent_auth, pam_ssh_agent_auth-debuginfo | 0:0.10.3-7.24.el8 | RHSA-2024:3166 |
| AlmaLinux | 8 | openssh, openssh-cavs, openssh-ldap and 4 more | 8.0p1-24.el8 | ALSA-2024:3166 |
| AlmaLinux | 8 | pam_ssh_agent_auth | 0.10.3-7.24.el8 | ALSA-2024:3166 |
| Rocky Linux | 8 | openssh | 0:8.0p1-24.el8 | RLSA-2024:3166 |
| Alpine | v3.19, v3.20, v3.21 and 3 more | openssh | 8.3_p1-r0 | ALPINE-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 rates this Moderate.
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.
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
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 8 | openssh-0:8.0p1-24.el8 | Fixed 2024-05-22 | RHSA-2024:3166 |
| Red Hat Enterprise Linux 5 | openssh | Out of support scope | |
| Red Hat Enterprise Linux 6 | openssh | Out of support scope | |
| Red Hat Enterprise Linux 7 | openssh | Will 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.
| Advisory | Title | Published | Sectors | Affected | Fixed |
|---|---|---|---|---|---|
| ICSA-23-348-10 | Siemens SIMATIC S7-1500 | 2023-12-12 | Critical Manufacturing, Transportation Systems, Energy, Healthcare and Public Health, Financial Services, Government Services and Facilities | SIMATIC 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 more | none 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.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.