CVE-2018-20685

lowpriority · track · 22OT risk · elevatedEPSS 0.037 · 90 %ileDEEURUUS
grimoire priorityP3 · Track
Exploitable?
—
no known exploitation
Likely / severe?
3.68% (90th) EPSS
CVSS 2.6 · low
Is it mine?
193 products
Check your exposure
Who says so?
7 sources
cnnvd · enisa_euvd · fstec_bdu · cert_bund

EPSS · scored 2026-10-26

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.

01

remediations

Vendor fix, mitigation, or workaround guidance, as published by each source.

A vendor fix is available.

  • Fixedopenssh-0:8.0p1-3.el8.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-0:8.0p1-3.el8.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-0:8.0p1-3.el8.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-0:8.0p1-3.el8.src as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-0:8.0p1-3.el8.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-askpass-0:8.0p1-3.el8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-askpass-0:8.0p1-3.el8.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-askpass-0:8.0p1-3.el8.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-askpass-0:8.0p1-3.el8.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-askpass-debuginfo-0:8.0p1-3.el8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-askpass-debuginfo-0:8.0p1-3.el8.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-askpass-debuginfo-0:8.0p1-3.el8.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-askpass-debuginfo-0:8.0p1-3.el8.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-askpass-debuginfo-0:8.0p1-3.el8.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-askpass-debuginfo-0:8.0p1-3.el8.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-askpass-debuginfo-0:8.0p1-3.el8.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-askpass-debuginfo-0:8.0p1-3.el8.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-cavs-0:8.0p1-3.el8.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-cavs-0:8.0p1-3.el8.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-cavs-0:8.0p1-3.el8.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-cavs-0:8.0p1-3.el8.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-cavs-debuginfo-0:8.0p1-3.el8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-cavs-debuginfo-0:8.0p1-3.el8.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-cavs-debuginfo-0:8.0p1-3.el8.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-cavs-debuginfo-0:8.0p1-3.el8.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-cavs-debuginfo-0:8.0p1-3.el8.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-cavs-debuginfo-0:8.0p1-3.el8.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-cavs-debuginfo-0:8.0p1-3.el8.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-cavs-debuginfo-0:8.0p1-3.el8.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-clients-0:8.0p1-3.el8.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-clients-0:8.0p1-3.el8.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-clients-0:8.0p1-3.el8.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-clients-0:8.0p1-3.el8.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-clients-debuginfo-0:8.0p1-3.el8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-clients-debuginfo-0:8.0p1-3.el8.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-clients-debuginfo-0:8.0p1-3.el8.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-clients-debuginfo-0:8.0p1-3.el8.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-clients-debuginfo-0:8.0p1-3.el8.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-clients-debuginfo-0:8.0p1-3.el8.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-clients-debuginfo-0:8.0p1-3.el8.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-clients-debuginfo-0:8.0p1-3.el8.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-debuginfo-0:8.0p1-3.el8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-debuginfo-0:8.0p1-3.el8.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-debuginfo-0:8.0p1-3.el8.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-debuginfo-0:8.0p1-3.el8.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-debuginfo-0:8.0p1-3.el8.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-debuginfo-0:8.0p1-3.el8.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-debuginfo-0:8.0p1-3.el8.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-debuginfo-0:8.0p1-3.el8.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-debugsource-0:8.0p1-3.el8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-debugsource-0:8.0p1-3.el8.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-debugsource-0:8.0p1-3.el8.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-debugsource-0:8.0p1-3.el8.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-debugsource-0:8.0p1-3.el8.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-debugsource-0:8.0p1-3.el8.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-debugsource-0:8.0p1-3.el8.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-debugsource-0:8.0p1-3.el8.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-keycat-0:8.0p1-3.el8.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-keycat-0:8.0p1-3.el8.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-keycat-0:8.0p1-3.el8.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-keycat-0:8.0p1-3.el8.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-keycat-debuginfo-0:8.0p1-3.el8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-keycat-debuginfo-0:8.0p1-3.el8.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-keycat-debuginfo-0:8.0p1-3.el8.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-keycat-debuginfo-0:8.0p1-3.el8.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-keycat-debuginfo-0:8.0p1-3.el8.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-keycat-debuginfo-0:8.0p1-3.el8.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-keycat-debuginfo-0:8.0p1-3.el8.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-keycat-debuginfo-0:8.0p1-3.el8.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-ldap-0:8.0p1-3.el8.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-ldap-0:8.0p1-3.el8.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-ldap-0:8.0p1-3.el8.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-ldap-0:8.0p1-3.el8.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-ldap-debuginfo-0:8.0p1-3.el8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-ldap-debuginfo-0:8.0p1-3.el8.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-ldap-debuginfo-0:8.0p1-3.el8.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-ldap-debuginfo-0:8.0p1-3.el8.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-ldap-debuginfo-0:8.0p1-3.el8.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-ldap-debuginfo-0:8.0p1-3.el8.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-ldap-debuginfo-0:8.0p1-3.el8.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-ldap-debuginfo-0:8.0p1-3.el8.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-server-0:8.0p1-3.el8.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-server-0:8.0p1-3.el8.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-server-0:8.0p1-3.el8.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-server-0:8.0p1-3.el8.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-server-debuginfo-0:8.0p1-3.el8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-server-debuginfo-0:8.0p1-3.el8.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-server-debuginfo-0:8.0p1-3.el8.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-server-debuginfo-0:8.0p1-3.el8.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-server-debuginfo-0:8.0p1-3.el8.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-server-debuginfo-0:8.0p1-3.el8.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-server-debuginfo-0:8.0p1-3.el8.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedopenssh-server-debuginfo-0:8.0p1-3.el8.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedpam_ssh_agent_auth-0:0.10.3-7.3.el8.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedpam_ssh_agent_auth-0:0.10.3-7.3.el8.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedpam_ssh_agent_auth-0:0.10.3-7.3.el8.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedpam_ssh_agent_auth-0:0.10.3-7.3.el8.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedpam_ssh_agent_auth-debuginfo-0:0.10.3-7.3.el8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedpam_ssh_agent_auth-debuginfo-0:0.10.3-7.3.el8.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedpam_ssh_agent_auth-debuginfo-0:0.10.3-7.3.el8.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedpam_ssh_agent_auth-debuginfo-0:0.10.3-7.3.el8.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedpam_ssh_agent_auth-debuginfo-0:0.10.3-7.3.el8.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedpam_ssh_agent_auth-debuginfo-0:0.10.3-7.3.el8.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedpam_ssh_agent_auth-debuginfo-0:0.10.3-7.3.el8.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • Fixedpam_ssh_agent_auth-debuginfo-0:0.10.3-7.3.el8.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, the OpenSSH server daemon (sshd) will be restarted automatically.

    https://access.redhat.com/errata/RHSA-2019:3702
  • FixedSCALANCE X204RNA (HSR) (6GK5204-0BA00-2MB2)siemens_psirt

    Update to V3.2.7 or later version

    https://support.industry.siemens.com/cs/ww/en/view/109814809/
  • FixedSCALANCE X204RNA (PRP) (6GK5204-0BA00-2KB2)siemens_psirt

    Update to V3.2.7 or later version

    https://support.industry.siemens.com/cs/ww/en/view/109814809/
  • FixedSCALANCE X204RNA EEC (HSR) (6GK5204-0BS00-2NA3)siemens_psirt

    Update to V3.2.7 or later version

    https://support.industry.siemens.com/cs/ww/en/view/109814809/
  • FixedSCALANCE X204RNA EEC (PRP) (6GK5204-0BS00-3LA3)siemens_psirt

    Update to V3.2.7 or later version

    https://support.industry.siemens.com/cs/ww/en/view/109814809/
  • FixedSCALANCE X204RNA EEC (PRP/HSR) (6GK5204-0BS00-3PA3)siemens_psirt

    Update to V3.2.7 or later version

    https://support.industry.siemens.com/cs/ww/en/view/109814809/
  • FixedSCALANCE X204RNA (HSR) (6GK5204-0BA00-2MB2)cisa_csaf_ot

    Update to V3.2.7 or later version

    https://support.industry.siemens.com/cs/ww/en/view/109814809/
  • FixedSCALANCE X204RNA (PRP) (6GK5204-0BA00-2KB2)cisa_csaf_ot

    Update to V3.2.7 or later version

    https://support.industry.siemens.com/cs/ww/en/view/109814809/
  • FixedSCALANCE X204RNA EEC (HSR) (6GK5204-0BS00-2NA3)cisa_csaf_ot

    Update to V3.2.7 or later version

    https://support.industry.siemens.com/cs/ww/en/view/109814809/
  • FixedSCALANCE X204RNA EEC (PRP) (6GK5204-0BS00-3LA3)cisa_csaf_ot

    Update to V3.2.7 or later version

    https://support.industry.siemens.com/cs/ww/en/view/109814809/
  • FixedSCALANCE X204RNA EEC (PRP/HSR) (6GK5204-0BS00-3PA3)cisa_csaf_ot

    Update to V3.2.7 or later version

    https://support.industry.siemens.com/cs/ww/en/view/109814809/
  • MitigationSCALANCE X204RNA (HSR) (6GK5204-0BA00-2MB2)siemens_psirt

    Deactivate the webserver if not required, and if deactivation is supported by the product

  • MitigationSCALANCE X204RNA (PRP) (6GK5204-0BA00-2KB2)siemens_psirt

    Deactivate the webserver if not required, and if deactivation is supported by the product

  • MitigationSCALANCE X204RNA EEC (HSR) (6GK5204-0BS00-2NA3)siemens_psirt

    Deactivate the webserver if not required, and if deactivation is supported by the product

  • MitigationSCALANCE X204RNA EEC (PRP) (6GK5204-0BS00-3LA3)siemens_psirt

    Deactivate the webserver if not required, and if deactivation is supported by the product

  • MitigationSCALANCE X204RNA EEC (PRP/HSR) (6GK5204-0BS00-3PA3)siemens_psirt

    Deactivate the webserver if not required, and if deactivation is supported by the product

  • MitigationSCALANCE X204RNA (HSR) (6GK5204-0BA00-2MB2)cisa_csaf_ot

    Deactivate the webserver if not required, and if deactivation is supported by the product

  • MitigationSCALANCE X204RNA (PRP) (6GK5204-0BA00-2KB2)cisa_csaf_ot

    Deactivate the webserver if not required, and if deactivation is supported by the product

  • MitigationSCALANCE X204RNA EEC (HSR) (6GK5204-0BS00-2NA3)cisa_csaf_ot

    Deactivate the webserver if not required, and if deactivation is supported by the product

  • MitigationSCALANCE X204RNA EEC (PRP) (6GK5204-0BS00-3LA3)cisa_csaf_ot

    Deactivate the webserver if not required, and if deactivation is supported by the product

  • MitigationSCALANCE X204RNA EEC (PRP/HSR) (6GK5204-0BS00-3PA3)cisa_csaf_ot

    Deactivate the webserver if not required, and if deactivation is supported by the product

  • Workaroundopenssh-0:8.0p1-3.el8.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-0:8.0p1-3.el8.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-0:8.0p1-3.el8.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-0:8.0p1-3.el8.src as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-0:8.0p1-3.el8.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-askpass-0:8.0p1-3.el8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-askpass-0:8.0p1-3.el8.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-askpass-0:8.0p1-3.el8.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-askpass-0:8.0p1-3.el8.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-askpass-debuginfo-0:8.0p1-3.el8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-askpass-debuginfo-0:8.0p1-3.el8.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-askpass-debuginfo-0:8.0p1-3.el8.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-askpass-debuginfo-0:8.0p1-3.el8.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-askpass-debuginfo-0:8.0p1-3.el8.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-askpass-debuginfo-0:8.0p1-3.el8.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-askpass-debuginfo-0:8.0p1-3.el8.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-askpass-debuginfo-0:8.0p1-3.el8.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-cavs-0:8.0p1-3.el8.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-cavs-0:8.0p1-3.el8.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-cavs-0:8.0p1-3.el8.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-cavs-0:8.0p1-3.el8.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-cavs-debuginfo-0:8.0p1-3.el8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-cavs-debuginfo-0:8.0p1-3.el8.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-cavs-debuginfo-0:8.0p1-3.el8.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-cavs-debuginfo-0:8.0p1-3.el8.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-cavs-debuginfo-0:8.0p1-3.el8.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-cavs-debuginfo-0:8.0p1-3.el8.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-cavs-debuginfo-0:8.0p1-3.el8.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-cavs-debuginfo-0:8.0p1-3.el8.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-clients-0:8.0p1-3.el8.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-clients-0:8.0p1-3.el8.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-clients-0:8.0p1-3.el8.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-clients-0:8.0p1-3.el8.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-clients-debuginfo-0:8.0p1-3.el8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-clients-debuginfo-0:8.0p1-3.el8.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-clients-debuginfo-0:8.0p1-3.el8.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-clients-debuginfo-0:8.0p1-3.el8.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-clients-debuginfo-0:8.0p1-3.el8.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-clients-debuginfo-0:8.0p1-3.el8.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-clients-debuginfo-0:8.0p1-3.el8.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-clients-debuginfo-0:8.0p1-3.el8.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-debuginfo-0:8.0p1-3.el8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-debuginfo-0:8.0p1-3.el8.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-debuginfo-0:8.0p1-3.el8.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-debuginfo-0:8.0p1-3.el8.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-debuginfo-0:8.0p1-3.el8.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-debuginfo-0:8.0p1-3.el8.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-debuginfo-0:8.0p1-3.el8.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-debuginfo-0:8.0p1-3.el8.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-debugsource-0:8.0p1-3.el8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-debugsource-0:8.0p1-3.el8.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-debugsource-0:8.0p1-3.el8.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-debugsource-0:8.0p1-3.el8.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-debugsource-0:8.0p1-3.el8.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-debugsource-0:8.0p1-3.el8.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-debugsource-0:8.0p1-3.el8.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-debugsource-0:8.0p1-3.el8.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-keycat-0:8.0p1-3.el8.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-keycat-0:8.0p1-3.el8.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-keycat-0:8.0p1-3.el8.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-keycat-0:8.0p1-3.el8.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-keycat-debuginfo-0:8.0p1-3.el8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-keycat-debuginfo-0:8.0p1-3.el8.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-keycat-debuginfo-0:8.0p1-3.el8.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-keycat-debuginfo-0:8.0p1-3.el8.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-keycat-debuginfo-0:8.0p1-3.el8.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-keycat-debuginfo-0:8.0p1-3.el8.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-keycat-debuginfo-0:8.0p1-3.el8.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-keycat-debuginfo-0:8.0p1-3.el8.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-ldap-0:8.0p1-3.el8.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-ldap-0:8.0p1-3.el8.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-ldap-0:8.0p1-3.el8.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-ldap-0:8.0p1-3.el8.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-ldap-debuginfo-0:8.0p1-3.el8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-ldap-debuginfo-0:8.0p1-3.el8.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-ldap-debuginfo-0:8.0p1-3.el8.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-ldap-debuginfo-0:8.0p1-3.el8.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-ldap-debuginfo-0:8.0p1-3.el8.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-ldap-debuginfo-0:8.0p1-3.el8.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-ldap-debuginfo-0:8.0p1-3.el8.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-ldap-debuginfo-0:8.0p1-3.el8.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-server-0:8.0p1-3.el8.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-server-0:8.0p1-3.el8.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-server-0:8.0p1-3.el8.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-server-0:8.0p1-3.el8.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-server-debuginfo-0:8.0p1-3.el8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-server-debuginfo-0:8.0p1-3.el8.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-server-debuginfo-0:8.0p1-3.el8.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-server-debuginfo-0:8.0p1-3.el8.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-server-debuginfo-0:8.0p1-3.el8.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-server-debuginfo-0:8.0p1-3.el8.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-server-debuginfo-0:8.0p1-3.el8.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundopenssh-server-debuginfo-0:8.0p1-3.el8.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundpam_ssh_agent_auth-0:0.10.3-7.3.el8.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundpam_ssh_agent_auth-0:0.10.3-7.3.el8.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundpam_ssh_agent_auth-0:0.10.3-7.3.el8.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundpam_ssh_agent_auth-0:0.10.3-7.3.el8.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundpam_ssh_agent_auth-debuginfo-0:0.10.3-7.3.el8.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundpam_ssh_agent_auth-debuginfo-0:0.10.3-7.3.el8.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundpam_ssh_agent_auth-debuginfo-0:0.10.3-7.3.el8.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundpam_ssh_agent_auth-debuginfo-0:0.10.3-7.3.el8.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundpam_ssh_agent_auth-debuginfo-0:0.10.3-7.3.el8.s390x as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundpam_ssh_agent_auth-debuginfo-0:0.10.3-7.3.el8.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundpam_ssh_agent_auth-debuginfo-0:0.10.3-7.3.el8.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

  • Workaroundpam_ssh_agent_auth-debuginfo-0:0.10.3-7.3.el8.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf

    This issue only affects the users of scp binary which is a part of openssh-clients package. Other usage of SSH protocol or other ssh clients is not affected. 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. Note: To exploit this flaw, the victim needs to connect to a malicious SSH server or MITM (Man-in-the-middle) the scp connection, both of which can be detected by the system administrator via a change in the host key of the SSH server. Further, if connections via scp are made to only trusted SSH servers, then those use-cases are not vulnerable to this security flaw.

02

cvss

Technical severity, 0–10. One row per scoring source.

5.3
010

base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · low–medium · 2.6–5.3

v2.02.6lowAV:N/AC:H/Au:N/C:N/I:P/A:Nprimary · NVD / NIST USexploitability 4.9 · impact 2.9
v3.15.3mediumCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:Nprimary · NVD / NIST USexploitability 1.6 · impact 3.6
v3.05.3mediumCVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:N/A:Nsecondary · Red Hat Product Security US
v3.15.3mediumAV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:Nsecondary · FSTEC (BDU) RU
v3.15.3mediumCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:Nsecondary · ENISA EU
v3.15.3mediumCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:Nsecondaryexploitability 1.6 · impact 3.6
v3.15.3mediumCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N/E:P/RL:O/RC:Csecondary · Siemens ProductCERT DE
v3.15.3mediumCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N/E:Hsecondary · CVSS-BT (t0sche)
v3.15.3mediumCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:H/A:N/E:P/RL:O/RC:Csecondary · CISA US
03

ssvc

A stakeholder decision — act, attend, or track — from exploitation and impact.

Trackcoordinatorcisa_ssvcUS
04

weaknesses

The CWE weakness classes this flaw belongs to.

CWE-863USprimaryCWE-20USCWE-284USCWE-863USCWE-863US
05

affected products (193)

Products and version ranges known to be affected.

showing 20 of 193
06

advisories (5)

Vendor and ecosystem advisories describing this.

  • RHSA-2019:3702Red Hat Security Advisory: openssh security, bug fix, and enhancement update2019-11-05csaf · redhat_csafUS

    An update for openssh is now available for Red Hat Enterprise Linux 8. Red Hat Product Security has rated this update as having a security impact of Moderate. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) in the References section.

  • SSA-412672SSA-412672: Multiple OpenSSL and OpenSSH Vulnerabilities in SCALANCE X-200RNA Switch Devices before V3.2.72022-12-13csaf · siemens_psirtDE

    SCALANCE X-200RNA switch devices before V3.2.7 contain multiple OpenSSL and OpenSSH vulnerabilities. The most severe of these vulnerabilities could allow a denial of service condition or could lead to execution of arbitrary code. Siemens has released updates for the affected products and recommends to update to the latest versions.

  • WID-SEC-W-2024-0872OpenSSH: Schwachstelle ermöglicht Umgehen von SicherheitsvorkehrungenDeutsch2019-01-10csaf · cert_bundDE

    Ein entfernter, authentisierter Angreifer kann eine Schwachstelle in OpenSSH ausnutzen, um Sicherheitsvorkehrungen zu umgehen.

  • WID-SEC-W-2024-1082Juniper JUNOS: Mehrere SchwachstellenDeutsch2024-05-09csaf · cert_bundDE

    Ein Angreifer kann mehrere Schwachstellen in Juniper JUNOS im Zusammenhang mit OpenSSH ausnutzen, um Sicherheitsmaßnahmen zu umgehen, beliebigen Code auszuführen oder Dateien zu manipulieren.

  • ICSA-22-349-21Siemens SCALANCE X-200RNA Switch Devices2022-12-13icsa · cisa_csaf_otUS

    SCALANCE X-200RNA switch devices before V3.2.7 contain multiple OpenSSL and OpenSSH vulnerabilities. The most severe of these vulnerabilities could allow a denial of service condition or could lead to execution of arbitrary code. Siemens has released updates for the affected products and recommends to update to the latest versions.

07

also known as (4)

Other names and identifiers for this entity.

08

sources

Which sources assert this record, and when.

cnnvdenisa_euvdfstec_bducert_bundcisa_csaf_otredhat_csafsiemens_psirtNVDCVE.orgMITRE
published 2019-01-10modified 2026-06-17
10

references (62)

External citations — patches, advisories, analysis.

scry

Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.

Free scan