CVE-2022-29154
highpriority · track · 41OT risk · elevatedEPSS 0.023 · 84 %ileexploit · PoCCHDEEURUUSEPSS · scored 2026-10-27
An issue was discovered in rsync before 3.2.5 that allows malicious remote servers to write arbitrary files inside the directories of connecting peers. The server chooses which files/directories are sent to the client. However, the rsync client performs insufficient validation of file names. A malicious rsync server (or Man-in-The-Middle attacker) can overwrite arbitrary files in the rsync client target directory and subdirectories (for example, overwrite the .ssh/authorized_keys file).
remediations
Vendor fix, mitigation, or workaround guidance, as published by each source.
A vendor fix is available.
- Fixedrsync-0:3.1.2-11.el7_9.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7)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
https://access.redhat.com/errata/RHSA-2022:6170 - Fixedrsync-0:3.1.2-11.el7_9.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7)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
https://access.redhat.com/errata/RHSA-2022:6170 - Fixedrsync-0:3.1.2-11.el7_9.s390x as a component of Red Hat Enterprise Linux Server (v. 7)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
https://access.redhat.com/errata/RHSA-2022:6170 - Fixedrsync-0:3.1.2-11.el7_9.src as a component of Red Hat Enterprise Linux Client (v. 7)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
https://access.redhat.com/errata/RHSA-2022:6170 - Fixedrsync-0:3.1.2-11.el7_9.src as a component of Red Hat Enterprise Linux Server (v. 7)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
https://access.redhat.com/errata/RHSA-2022:6170 - Fixedrsync-0:3.1.2-11.el7_9.src as a component of Red Hat Enterprise Linux Workstation (v. 7)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
https://access.redhat.com/errata/RHSA-2022:6170 - Fixedrsync-0:3.1.2-11.el7_9.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7)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
https://access.redhat.com/errata/RHSA-2022:6170 - Fixedrsync-0:3.1.2-11.el7_9.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7)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
https://access.redhat.com/errata/RHSA-2022:6170 - Fixedrsync-0:3.1.2-11.el7_9.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 7)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
https://access.redhat.com/errata/RHSA-2022:6170 - Fixedrsync-debuginfo-0:3.1.2-11.el7_9.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7)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
https://access.redhat.com/errata/RHSA-2022:6170 - Fixedrsync-debuginfo-0:3.1.2-11.el7_9.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7)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
https://access.redhat.com/errata/RHSA-2022:6170 - Fixedrsync-debuginfo-0:3.1.2-11.el7_9.s390x as a component of Red Hat Enterprise Linux Server (v. 7)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
https://access.redhat.com/errata/RHSA-2022:6170 - Fixedrsync-debuginfo-0:3.1.2-11.el7_9.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7)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
https://access.redhat.com/errata/RHSA-2022:6170 - Fixedrsync-debuginfo-0:3.1.2-11.el7_9.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7)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
https://access.redhat.com/errata/RHSA-2022:6170 - Fixedrsync-debuginfo-0:3.1.2-11.el7_9.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 7)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
https://access.redhat.com/errata/RHSA-2022:6170 - Fixedrsync-0:3.1.3-12.el8_4.2.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.4)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
https://access.redhat.com/errata/RHSA-2022:6171 - Fixedrsync-0:3.1.3-12.el8_4.2.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.4)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
https://access.redhat.com/errata/RHSA-2022:6171 - Fixedrsync-0:3.1.3-12.el8_4.2.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.4)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
https://access.redhat.com/errata/RHSA-2022:6171 - Fixedrsync-0:3.1.3-12.el8_4.2.src as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.4)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
https://access.redhat.com/errata/RHSA-2022:6171 - Fixedrsync-0:3.1.3-12.el8_4.2.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.4)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
https://access.redhat.com/errata/RHSA-2022:6171 - Fixedrsync-daemon-0:3.1.3-12.el8_4.2.noarch as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.4)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
https://access.redhat.com/errata/RHSA-2022:6171 - Fixedrsync-debuginfo-0:3.1.3-12.el8_4.2.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.4)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
https://access.redhat.com/errata/RHSA-2022:6171 - Fixedrsync-debuginfo-0:3.1.3-12.el8_4.2.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.4)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
https://access.redhat.com/errata/RHSA-2022:6171 - Fixedrsync-debuginfo-0:3.1.3-12.el8_4.2.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.4)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
https://access.redhat.com/errata/RHSA-2022:6171 - Fixedrsync-debuginfo-0:3.1.3-12.el8_4.2.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.4)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
https://access.redhat.com/errata/RHSA-2022:6171 - Fixedrsync-debugsource-0:3.1.3-12.el8_4.2.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.4)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
https://access.redhat.com/errata/RHSA-2022:6171 - Fixedrsync-debugsource-0:3.1.3-12.el8_4.2.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.4)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
https://access.redhat.com/errata/RHSA-2022:6171 - Fixedrsync-debugsource-0:3.1.3-12.el8_4.2.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.4)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
https://access.redhat.com/errata/RHSA-2022:6171 - Fixedrsync-debugsource-0:3.1.3-12.el8_4.2.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.4)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
https://access.redhat.com/errata/RHSA-2022:6171 - Fixedrsync-0:3.1.3-7.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)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
https://access.redhat.com/errata/RHSA-2022:6172 - Fixedrsync-0:3.1.3-7.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)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
https://access.redhat.com/errata/RHSA-2022:6172 - Fixedrsync-0:3.1.3-7.el8_2.2.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)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
https://access.redhat.com/errata/RHSA-2022:6172 - Fixedrsync-0:3.1.3-7.el8_2.2.src as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)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
https://access.redhat.com/errata/RHSA-2022:6172 - Fixedrsync-0:3.1.3-7.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)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
https://access.redhat.com/errata/RHSA-2022:6172 - Fixedrsync-daemon-0:3.1.3-7.el8_2.2.noarch as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)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
https://access.redhat.com/errata/RHSA-2022:6172 - Fixedrsync-debuginfo-0:3.1.3-7.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)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
https://access.redhat.com/errata/RHSA-2022:6172 - Fixedrsync-debuginfo-0:3.1.3-7.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)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
https://access.redhat.com/errata/RHSA-2022:6172 - Fixedrsync-debuginfo-0:3.1.3-7.el8_2.2.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)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
https://access.redhat.com/errata/RHSA-2022:6172 - Fixedrsync-debuginfo-0:3.1.3-7.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)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
https://access.redhat.com/errata/RHSA-2022:6172 - Fixedrsync-debugsource-0:3.1.3-7.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)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
https://access.redhat.com/errata/RHSA-2022:6172 - Fixedrsync-debugsource-0:3.1.3-7.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)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
https://access.redhat.com/errata/RHSA-2022:6172 - Fixedrsync-debugsource-0:3.1.3-7.el8_2.2.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)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
https://access.redhat.com/errata/RHSA-2022:6172 - Fixedrsync-debugsource-0:3.1.3-7.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)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
https://access.redhat.com/errata/RHSA-2022:6172 - Fixedrsync-0:3.1.3-6.el8_1.2.ppc64le as a component of Red Hat Enterprise Linux BaseOS E4S (v. 8.1)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
https://access.redhat.com/errata/RHSA-2022:6173 - Fixedrsync-0:3.1.3-6.el8_1.2.src as a component of Red Hat Enterprise Linux BaseOS E4S (v. 8.1)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
https://access.redhat.com/errata/RHSA-2022:6173 - Fixedrsync-0:3.1.3-6.el8_1.2.x86_64 as a component of Red Hat Enterprise Linux BaseOS E4S (v. 8.1)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
https://access.redhat.com/errata/RHSA-2022:6173 - Fixedrsync-daemon-0:3.1.3-6.el8_1.2.noarch as a component of Red Hat Enterprise Linux BaseOS E4S (v. 8.1)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
https://access.redhat.com/errata/RHSA-2022:6173 - Fixedrsync-debuginfo-0:3.1.3-6.el8_1.2.ppc64le as a component of Red Hat Enterprise Linux BaseOS E4S (v. 8.1)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
https://access.redhat.com/errata/RHSA-2022:6173 - Fixedrsync-debuginfo-0:3.1.3-6.el8_1.2.x86_64 as a component of Red Hat Enterprise Linux BaseOS E4S (v. 8.1)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
https://access.redhat.com/errata/RHSA-2022:6173 - Fixedrsync-debugsource-0:3.1.3-6.el8_1.2.ppc64le as a component of Red Hat Enterprise Linux BaseOS E4S (v. 8.1)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
https://access.redhat.com/errata/RHSA-2022:6173 - Fixedrsync-debugsource-0:3.1.3-6.el8_1.2.x86_64 as a component of Red Hat Enterprise Linux BaseOS E4S (v. 8.1)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
https://access.redhat.com/errata/RHSA-2022:6173 - Fixedrsync-0:3.1.3-14.el8_6.3.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
https://access.redhat.com/errata/RHSA-2022:6180 - Fixedrsync-0:3.1.3-14.el8_6.3.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
https://access.redhat.com/errata/RHSA-2022:6180 - Fixedrsync-0:3.1.3-14.el8_6.3.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
https://access.redhat.com/errata/RHSA-2022:6180 - Fixedrsync-0:3.1.3-14.el8_6.3.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
https://access.redhat.com/errata/RHSA-2022:6180 - Fixedrsync-0:3.1.3-14.el8_6.3.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
https://access.redhat.com/errata/RHSA-2022:6180 - Fixedrsync-daemon-0:3.1.3-14.el8_6.3.noarch 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
https://access.redhat.com/errata/RHSA-2022:6180 - Fixedrsync-debuginfo-0:3.1.3-14.el8_6.3.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
https://access.redhat.com/errata/RHSA-2022:6180 - Fixedrsync-debuginfo-0:3.1.3-14.el8_6.3.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
https://access.redhat.com/errata/RHSA-2022:6180 - Fixedrsync-debuginfo-0:3.1.3-14.el8_6.3.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
https://access.redhat.com/errata/RHSA-2022:6180 - Fixedrsync-debuginfo-0:3.1.3-14.el8_6.3.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
https://access.redhat.com/errata/RHSA-2022:6180 - Fixedrsync-debugsource-0:3.1.3-14.el8_6.3.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
https://access.redhat.com/errata/RHSA-2022:6180 - Fixedrsync-debugsource-0:3.1.3-14.el8_6.3.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
https://access.redhat.com/errata/RHSA-2022:6180 - Fixedrsync-debugsource-0:3.1.3-14.el8_6.3.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
https://access.redhat.com/errata/RHSA-2022:6180 - Fixedrsync-debugsource-0:3.1.3-14.el8_6.3.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
https://access.redhat.com/errata/RHSA-2022:6180 - Fixedrsync-0:3.2.3-9.el9_0.2.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 9)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
https://access.redhat.com/errata/RHSA-2022:6181 - Fixedrsync-0:3.2.3-9.el9_0.2.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 9)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
https://access.redhat.com/errata/RHSA-2022:6181 - Fixedrsync-0:3.2.3-9.el9_0.2.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 9)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
https://access.redhat.com/errata/RHSA-2022:6181 - Fixedrsync-0:3.2.3-9.el9_0.2.src as a component of Red Hat Enterprise Linux BaseOS (v. 9)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
https://access.redhat.com/errata/RHSA-2022:6181 - Fixedrsync-0:3.2.3-9.el9_0.2.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 9)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
https://access.redhat.com/errata/RHSA-2022:6181 - Fixedrsync-daemon-0:3.2.3-9.el9_0.2.noarch as a component of Red Hat Enterprise Linux AppStream (v. 9)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
https://access.redhat.com/errata/RHSA-2022:6181 - Fixedrsync-debuginfo-0:3.2.3-9.el9_0.2.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 9)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
https://access.redhat.com/errata/RHSA-2022:6181 - Fixedrsync-debuginfo-0:3.2.3-9.el9_0.2.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 9)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
https://access.redhat.com/errata/RHSA-2022:6181 - Fixedrsync-debuginfo-0:3.2.3-9.el9_0.2.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 9)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
https://access.redhat.com/errata/RHSA-2022:6181 - Fixedrsync-debuginfo-0:3.2.3-9.el9_0.2.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 9)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
https://access.redhat.com/errata/RHSA-2022:6181 - Fixedrsync-debugsource-0:3.2.3-9.el9_0.2.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 9)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
https://access.redhat.com/errata/RHSA-2022:6181 - Fixedrsync-debugsource-0:3.2.3-9.el9_0.2.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 9)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
https://access.redhat.com/errata/RHSA-2022:6181 - Fixedrsync-debugsource-0:3.2.3-9.el9_0.2.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 9)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
https://access.redhat.com/errata/RHSA-2022:6181 - Fixedrsync-debugsource-0:3.2.3-9.el9_0.2.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 9)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
https://access.redhat.com/errata/RHSA-2022:6181 - FixedSCALANCE XCH328 (6GK5328-4TS01-2EC2)siemens_psirt
Update to V2.4 or later version
https://support.industry.siemens.com/cs/ww/en/view/109826613/ - FixedSCALANCE XCM324 (6GK5324-8TS01-2AC2)siemens_psirt
Update to V2.4 or later version
https://support.industry.siemens.com/cs/ww/en/view/109826613/ - FixedSCALANCE XCM328 (6GK5328-4TS01-2AC2)siemens_psirt
Update to V2.4 or later version
https://support.industry.siemens.com/cs/ww/en/view/109826613/ - FixedSCALANCE XCM332 (6GK5332-0GA01-2AC2)siemens_psirt
Update to V2.4 or later version
https://support.industry.siemens.com/cs/ww/en/view/109826613/ - FixedSCALANCE XRH334 (24 V DC, 8xFO, CC) (6GK5334-2TS01-2ER3)siemens_psirt
Update to V2.4 or later version
https://support.industry.siemens.com/cs/ww/en/view/109826613/ - FixedSCALANCE XRM334 (230 V AC, 12xFO) (6GK5334-3TS01-3AR3)siemens_psirt
Update to V2.4 or later version
https://support.industry.siemens.com/cs/ww/en/view/109826613/ - FixedSCALANCE XRM334 (230 V AC, 8xFO) (6GK5334-2TS01-3AR3)siemens_psirt
Update to V2.4 or later version
https://support.industry.siemens.com/cs/ww/en/view/109826613/ - FixedSCALANCE XRM334 (24 V DC, 12xFO) (6GK5334-3TS01-2AR3)siemens_psirt
Update to V2.4 or later version
https://support.industry.siemens.com/cs/ww/en/view/109826613/ - FixedSCALANCE XRM334 (24 V DC, 8xFO) (6GK5334-2TS01-2AR3)siemens_psirt
Update to V2.4 or later version
https://support.industry.siemens.com/cs/ww/en/view/109826613/ - FixedSCALANCE XRM334 (2x230 V AC, 12xFO) (6GK5334-3TS01-4AR3)siemens_psirt
Update to V2.4 or later version
https://support.industry.siemens.com/cs/ww/en/view/109826613/ - FixedSCALANCE XRM334 (2x230 V AC, 8xFO) (6GK5334-2TS01-4AR3)siemens_psirt
Update to V2.4 or later version
https://support.industry.siemens.com/cs/ww/en/view/109826613/ - FixedSCALANCE XCH328 (6GK5328-4TS01-2EC2)cisa_csaf_ot
Update to V2.4 or later version
https://support.industry.siemens.com/cs/ww/en/view/109826613/ - FixedSCALANCE XCM324 (6GK5324-8TS01-2AC2)cisa_csaf_ot
Update to V2.4 or later version
https://support.industry.siemens.com/cs/ww/en/view/109826613/ - FixedSCALANCE XCM328 (6GK5328-4TS01-2AC2)cisa_csaf_ot
Update to V2.4 or later version
https://support.industry.siemens.com/cs/ww/en/view/109826613/ - FixedSCALANCE XCM332 (6GK5332-0GA01-2AC2)cisa_csaf_ot
Update to V2.4 or later version
https://support.industry.siemens.com/cs/ww/en/view/109826613/ - FixedSCALANCE XRH334 (24 V DC, 8xFO, CC) (6GK5334-2TS01-2ER3)cisa_csaf_ot
Update to V2.4 or later version
https://support.industry.siemens.com/cs/ww/en/view/109826613/ - FixedSCALANCE XRM334 (230 V AC, 12xFO) (6GK5334-3TS01-3AR3)cisa_csaf_ot
Update to V2.4 or later version
https://support.industry.siemens.com/cs/ww/en/view/109826613/ - FixedSCALANCE XRM334 (230 V AC, 8xFO) (6GK5334-2TS01-3AR3)cisa_csaf_ot
Update to V2.4 or later version
https://support.industry.siemens.com/cs/ww/en/view/109826613/ - FixedSCALANCE XRM334 (24 V DC, 12xFO) (6GK5334-3TS01-2AR3)cisa_csaf_ot
Update to V2.4 or later version
https://support.industry.siemens.com/cs/ww/en/view/109826613/ - FixedSCALANCE XRM334 (24 V DC, 8xFO) (6GK5334-2TS01-2AR3)cisa_csaf_ot
Update to V2.4 or later version
https://support.industry.siemens.com/cs/ww/en/view/109826613/ - FixedSCALANCE XRM334 (2x230 V AC, 12xFO) (6GK5334-3TS01-4AR3)cisa_csaf_ot
Update to V2.4 or later version
https://support.industry.siemens.com/cs/ww/en/view/109826613/ - FixedSCALANCE XRM334 (2x230 V AC, 8xFO) (6GK5334-2TS01-4AR3)cisa_csaf_ot
Update to V2.4 or later version
https://support.industry.siemens.com/cs/ww/en/view/109826613/ - MitigationARM600abb_psirt
Mitigating factors describe conditions and circumstances that make an attack that exploits the vulnerability difficult or less likely to succeed. The following mitigations are recommended. 1. Obtain a cellular private access point (APN). A dedicated private cellular access point and respective SIM card subscriptions can be requested from your cellular service provider. This service doesn’t expose the traffic between remote sites and main site to the internet but rather uses cellular operator’s private wide area network (WAN). Therefore, the ARM600 wouldn’t need open ports to the internet. 2. Avoid exposing any system component to the internet. If, however, the ARM600 is exposed to the internet, only the VPN port should be opened towards the internet (e.g., Patrol management connections can be configured to use VPN tunnel and remote administration connections can be implemented by using OpenVPN PC-client). 4. Perform firewall configuration by the "allowlisting" principle, i.e., explicitly allowing only the required ports and protocols and blocking any other traffic. 6. If the internet is used as a WAN media for carrying VPN tunnels, use Demilitarized Zone (DMZ) for terminating connections from the internet (i.e., the remote connections should terminate to the DMZ network, which would be segregated from other networks by a firewall. The ARM600 server would be located into this DMZ). 7. Change the default user credentials of ARM600 and Arctic wireless gateways into non-defaults and use complex non-guessable passwords with special characters. Do not reuse passwords within the system. 8. Use administrator (i.e., root user) privileges only when required by the task. 9. Supporting systems, such as PCs used for configuration, should be frequently updated. If possible, use dedicated site PCs for upgrading and engineering purposes. At minimum, PCs should be investigated by running a full virus scan with recently updated signature files before introducing the PC to the OT system. Any data, such as device configurations and firmware update files transferred to the Arctic system should be virus scanned prior to transferring. 10. Introduce a backup policy, which will ensure periodical backups and backup revision numbering. Consider the following: a. Check that the entire system has backups available from all applicable parts. b. Store the backups in a safe place (e.g. in an encrypted storage), restricted by role-based access control mechanisms. c. Ensure the security of the configuration PCs that may have local copies of device configurations. d. Validate the backups to make sure that they’re working. 11. Follow cyber security best practices for installation, operation, and decommissioning as described in the product’s Cyber Security Deployment Guideline and User Manual. 12. Use continuous monitoring (e.g., intrusion detection/prevention tools) to detect anomalies in the system 13. Consider hardening the system according to the following: a. Remove any unnecessary communication links in the system. b. If possible, close unused physical ports. c. Open only the necessary TCP/UDP ports in the configuration. d. Remove all unnecessary user accounts. e. Restrict traffic by firewall. f. Allow the traffic only from/to necessary hosts' IP addresses (i.e., define both source and destination in the firewall rules, where possible). g. Define client IP address as allowed address in SCADA communication protocols, if such configuration is supported. h. Remove or deactivate all unused processes, communication ports and services, where possible. i. Use physical access controls to the system installations (e.g., to server rooms and device cabinets).
- MitigationSWabb_psirt
Mitigating factors describe conditions and circumstances that make an attack that exploits the vulnerability difficult or less likely to succeed. The following mitigations are recommended. 1. Obtain a cellular private access point (APN). A dedicated private cellular access point and respective SIM card subscriptions can be requested from your cellular service provider. This service doesn’t expose the traffic between remote sites and main site to the internet but rather uses cellular operator’s private wide area network (WAN). Therefore, the ARM600 wouldn’t need open ports to the internet. 2. Avoid exposing any system component to the internet. If, however, the ARM600 is exposed to the internet, only the VPN port should be opened towards the internet (e.g., Patrol management connections can be configured to use VPN tunnel and remote administration connections can be implemented by using OpenVPN PC-client). 4. Perform firewall configuration by the "allowlisting" principle, i.e., explicitly allowing only the required ports and protocols and blocking any other traffic. 6. If the internet is used as a WAN media for carrying VPN tunnels, use Demilitarized Zone (DMZ) for terminating connections from the internet (i.e., the remote connections should terminate to the DMZ network, which would be segregated from other networks by a firewall. The ARM600 server would be located into this DMZ). 7. Change the default user credentials of ARM600 and Arctic wireless gateways into non-defaults and use complex non-guessable passwords with special characters. Do not reuse passwords within the system. 8. Use administrator (i.e., root user) privileges only when required by the task. 9. Supporting systems, such as PCs used for configuration, should be frequently updated. If possible, use dedicated site PCs for upgrading and engineering purposes. At minimum, PCs should be investigated by running a full virus scan with recently updated signature files before introducing the PC to the OT system. Any data, such as device configurations and firmware update files transferred to the Arctic system should be virus scanned prior to transferring. 10. Introduce a backup policy, which will ensure periodical backups and backup revision numbering. Consider the following: a. Check that the entire system has backups available from all applicable parts. b. Store the backups in a safe place (e.g. in an encrypted storage), restricted by role-based access control mechanisms. c. Ensure the security of the configuration PCs that may have local copies of device configurations. d. Validate the backups to make sure that they’re working. 11. Follow cyber security best practices for installation, operation, and decommissioning as described in the product’s Cyber Security Deployment Guideline and User Manual. 12. Use continuous monitoring (e.g., intrusion detection/prevention tools) to detect anomalies in the system 13. Consider hardening the system according to the following: a. Remove any unnecessary communication links in the system. b. If possible, close unused physical ports. c. Open only the necessary TCP/UDP ports in the configuration. d. Remove all unnecessary user accounts. e. Restrict traffic by firewall. f. Allow the traffic only from/to necessary hosts' IP addresses (i.e., define both source and destination in the firewall rules, where possible). g. Define client IP address as allowed address in SCADA communication protocols, if such configuration is supported. h. Remove or deactivate all unused processes, communication ports and services, where possible. i. Use physical access controls to the system installations (e.g., to server rooms and device cabinets).
- MitigationARM600cisa_csaf_ot
Mitigating factors describe conditions and circumstances that make an attack that exploits the vulnerability difficult or less likely to succeed. The following mitigations are recommended. 1. Obtain a cellular private access point (APN). A dedicated private cellular access point and respective SIM card subscriptions can be requested from your cellular service provider. This service doesn’t expose the traffic between remote sites and main site to the internet but rather uses cellular operator’s private wide area network (WAN). Therefore, the ARM600 wouldn’t need open ports to the internet. 2. Avoid exposing any system component to the internet. If, however, the ARM600 is exposed to the internet, only the VPN port should be opened towards the internet (e.g., Patrol management connections can be configured to use VPN tunnel and remote administration connections can be implemented by using OpenVPN PC-client). 4. Perform firewall configuration by the "allowlisting" principle, i.e., explicitly allowing only the required ports and protocols and blocking any other traffic. 6. If the internet is used as a WAN media for carrying VPN tunnels, use Demilitarized Zone (DMZ) for terminating connections from the internet (i.e., the remote connections should terminate to the DMZ network, which would be segregated from other networks by a firewall. The ARM600 server would be located into this DMZ). 7. Change the default user credentials of ARM600 and Arctic wireless gateways into non-defaults and use complex non-guessable passwords with special characters. Do not reuse passwords within the system. 8. Use administrator (i.e., root user) privileges only when required by the task. 9. Supporting systems, such as PCs used for configuration, should be frequently updated. If possible, use dedicated site PCs for upgrading and engineering purposes. At minimum, PCs should be investigated by running a full virus scan with recently updated signature files before introducing the PC to the OT system. Any data, such as device configurations and firmware update files transferred to the Arctic system should be virus scanned prior to transferring. 10. Introduce a backup policy, which will ensure periodical backups and backup revision numbering. Consider the following: a. Check that the entire system has backups available from all applicable parts. b. Store the backups in a safe place (e.g. in an encrypted storage), restricted by role-based access control mechanisms. c. Ensure the security of the configuration PCs that may have local copies of device configurations. d. Validate the backups to make sure that they’re working. 11. Follow cyber security best practices for installation, operation, and decommissioning as described in the product’s Cyber Security Deployment Guideline and User Manual. 12. Use continuous monitoring (e.g., intrusion detection/prevention tools) to detect anomalies in the system 13. Consider hardening the system according to the following: a. Remove any unnecessary communication links in the system. b. If possible, close unused physical ports. c. Open only the necessary TCP/UDP ports in the configuration. d. Remove all unnecessary user accounts. e. Restrict traffic by firewall. f. Allow the traffic only from/to necessary hosts' IP addresses (i.e., define both source and destination in the firewall rules, where possible). g. Define client IP address as allowed address in SCADA communication protocols, if such configuration is supported. h. Remove or deactivate all unused processes, communication ports and services, where possible. i. Use physical access controls to the system installations (e.g., to server rooms and device cabinets).
- MitigationSWcisa_csaf_ot
Mitigating factors describe conditions and circumstances that make an attack that exploits the vulnerability difficult or less likely to succeed. The following mitigations are recommended. 1. Obtain a cellular private access point (APN). A dedicated private cellular access point and respective SIM card subscriptions can be requested from your cellular service provider. This service doesn’t expose the traffic between remote sites and main site to the internet but rather uses cellular operator’s private wide area network (WAN). Therefore, the ARM600 wouldn’t need open ports to the internet. 2. Avoid exposing any system component to the internet. If, however, the ARM600 is exposed to the internet, only the VPN port should be opened towards the internet (e.g., Patrol management connections can be configured to use VPN tunnel and remote administration connections can be implemented by using OpenVPN PC-client). 4. Perform firewall configuration by the "allowlisting" principle, i.e., explicitly allowing only the required ports and protocols and blocking any other traffic. 6. If the internet is used as a WAN media for carrying VPN tunnels, use Demilitarized Zone (DMZ) for terminating connections from the internet (i.e., the remote connections should terminate to the DMZ network, which would be segregated from other networks by a firewall. The ARM600 server would be located into this DMZ). 7. Change the default user credentials of ARM600 and Arctic wireless gateways into non-defaults and use complex non-guessable passwords with special characters. Do not reuse passwords within the system. 8. Use administrator (i.e., root user) privileges only when required by the task. 9. Supporting systems, such as PCs used for configuration, should be frequently updated. If possible, use dedicated site PCs for upgrading and engineering purposes. At minimum, PCs should be investigated by running a full virus scan with recently updated signature files before introducing the PC to the OT system. Any data, such as device configurations and firmware update files transferred to the Arctic system should be virus scanned prior to transferring. 10. Introduce a backup policy, which will ensure periodical backups and backup revision numbering. Consider the following: a. Check that the entire system has backups available from all applicable parts. b. Store the backups in a safe place (e.g. in an encrypted storage), restricted by role-based access control mechanisms. c. Ensure the security of the configuration PCs that may have local copies of device configurations. d. Validate the backups to make sure that they’re working. 11. Follow cyber security best practices for installation, operation, and decommissioning as described in the product’s Cyber Security Deployment Guideline and User Manual. 12. Use continuous monitoring (e.g., intrusion detection/prevention tools) to detect anomalies in the system 13. Consider hardening the system according to the following: a. Remove any unnecessary communication links in the system. b. If possible, close unused physical ports. c. Open only the necessary TCP/UDP ports in the configuration. d. Remove all unnecessary user accounts. e. Restrict traffic by firewall. f. Allow the traffic only from/to necessary hosts' IP addresses (i.e., define both source and destination in the firewall rules, where possible). g. Define client IP address as allowed address in SCADA communication protocols, if such configuration is supported. h. Remove or deactivate all unused processes, communication ports and services, where possible. i. Use physical access controls to the system installations (e.g., to server rooms and device cabinets).
- Workaroundrsync-0:3.1.2-11.el7_9.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-0:3.1.2-11.el7_9.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-0:3.1.2-11.el7_9.s390x as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-0:3.1.2-11.el7_9.src as a component of Red Hat Enterprise Linux Client (v. 7)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-0:3.1.2-11.el7_9.src as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-0:3.1.2-11.el7_9.src as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-0:3.1.2-11.el7_9.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-0:3.1.2-11.el7_9.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-0:3.1.2-11.el7_9.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-debuginfo-0:3.1.2-11.el7_9.ppc64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-debuginfo-0:3.1.2-11.el7_9.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-debuginfo-0:3.1.2-11.el7_9.s390x as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-debuginfo-0:3.1.2-11.el7_9.x86_64 as a component of Red Hat Enterprise Linux Client (v. 7)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-debuginfo-0:3.1.2-11.el7_9.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-debuginfo-0:3.1.2-11.el7_9.x86_64 as a component of Red Hat Enterprise Linux Workstation (v. 7)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-0:3.1.3-12.el8_4.2.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.4)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-0:3.1.3-12.el8_4.2.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.4)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-0:3.1.3-12.el8_4.2.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.4)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-0:3.1.3-12.el8_4.2.src as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.4)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-0:3.1.3-12.el8_4.2.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.4)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-daemon-0:3.1.3-12.el8_4.2.noarch as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.4)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-debuginfo-0:3.1.3-12.el8_4.2.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.4)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-debuginfo-0:3.1.3-12.el8_4.2.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.4)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-debuginfo-0:3.1.3-12.el8_4.2.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.4)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-debuginfo-0:3.1.3-12.el8_4.2.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.4)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-debugsource-0:3.1.3-12.el8_4.2.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.4)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-debugsource-0:3.1.3-12.el8_4.2.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.4)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-debugsource-0:3.1.3-12.el8_4.2.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.4)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-debugsource-0:3.1.3-12.el8_4.2.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v.8.4)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-0:3.1.3-7.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-0:3.1.3-7.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-0:3.1.3-7.el8_2.2.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-0:3.1.3-7.el8_2.2.src as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-0:3.1.3-7.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-daemon-0:3.1.3-7.el8_2.2.noarch as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-debuginfo-0:3.1.3-7.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-debuginfo-0:3.1.3-7.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-debuginfo-0:3.1.3-7.el8_2.2.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-debuginfo-0:3.1.3-7.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-debugsource-0:3.1.3-7.el8_2.2.aarch64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-debugsource-0:3.1.3-7.el8_2.2.ppc64le as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-debugsource-0:3.1.3-7.el8_2.2.s390x as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-debugsource-0:3.1.3-7.el8_2.2.x86_64 as a component of Red Hat Enterprise Linux BaseOS EUS (v. 8.2)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-0:3.1.3-6.el8_1.2.ppc64le as a component of Red Hat Enterprise Linux BaseOS E4S (v. 8.1)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-0:3.1.3-6.el8_1.2.src as a component of Red Hat Enterprise Linux BaseOS E4S (v. 8.1)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-0:3.1.3-6.el8_1.2.x86_64 as a component of Red Hat Enterprise Linux BaseOS E4S (v. 8.1)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-daemon-0:3.1.3-6.el8_1.2.noarch as a component of Red Hat Enterprise Linux BaseOS E4S (v. 8.1)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-debuginfo-0:3.1.3-6.el8_1.2.ppc64le as a component of Red Hat Enterprise Linux BaseOS E4S (v. 8.1)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-debuginfo-0:3.1.3-6.el8_1.2.x86_64 as a component of Red Hat Enterprise Linux BaseOS E4S (v. 8.1)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-debugsource-0:3.1.3-6.el8_1.2.ppc64le as a component of Red Hat Enterprise Linux BaseOS E4S (v. 8.1)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-debugsource-0:3.1.3-6.el8_1.2.x86_64 as a component of Red Hat Enterprise Linux BaseOS E4S (v. 8.1)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-0:3.1.3-14.el8_6.3.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-0:3.1.3-14.el8_6.3.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-0:3.1.3-14.el8_6.3.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-0:3.1.3-14.el8_6.3.src as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-0:3.1.3-14.el8_6.3.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-daemon-0:3.1.3-14.el8_6.3.noarch as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-debuginfo-0:3.1.3-14.el8_6.3.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-debuginfo-0:3.1.3-14.el8_6.3.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-debuginfo-0:3.1.3-14.el8_6.3.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-debuginfo-0:3.1.3-14.el8_6.3.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-debugsource-0:3.1.3-14.el8_6.3.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-debugsource-0:3.1.3-14.el8_6.3.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-debugsource-0:3.1.3-14.el8_6.3.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-debugsource-0:3.1.3-14.el8_6.3.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 8)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-0:3.2.3-9.el9_0.2.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 9)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-0:3.2.3-9.el9_0.2.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 9)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-0:3.2.3-9.el9_0.2.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 9)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-0:3.2.3-9.el9_0.2.src as a component of Red Hat Enterprise Linux BaseOS (v. 9)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-0:3.2.3-9.el9_0.2.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 9)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-daemon-0:3.2.3-9.el9_0.2.noarch as a component of Red Hat Enterprise Linux AppStream (v. 9)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-debuginfo-0:3.2.3-9.el9_0.2.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 9)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-debuginfo-0:3.2.3-9.el9_0.2.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 9)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-debuginfo-0:3.2.3-9.el9_0.2.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 9)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-debuginfo-0:3.2.3-9.el9_0.2.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 9)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-debugsource-0:3.2.3-9.el9_0.2.aarch64 as a component of Red Hat Enterprise Linux BaseOS (v. 9)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-debugsource-0:3.2.3-9.el9_0.2.ppc64le as a component of Red Hat Enterprise Linux BaseOS (v. 9)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-debugsource-0:3.2.3-9.el9_0.2.s390x as a component of Red Hat Enterprise Linux BaseOS (v. 9)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
- Workaroundrsync-debugsource-0:3.2.3-9.el9_0.2.x86_64 as a component of Red Hat Enterprise Linux BaseOS (v. 9)redhat_csaf
Only connecting to trusted Rsync servers over trusted channels would help to mitigate this flaw.
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · medium–high · 6.8–7.4
weaknesses
The CWE weakness classes this flaw belongs to.
exploits (1)
Public proof-of-concept and weaponised exploit code.
- EgeBalci/CVE-2022-29154HIP2022 presentation materials.PoC · poc_in_github
affected products (90)
Products and version ranges known to be affected.
advisories (15)
Vendor and ecosystem advisories describing this.
- 2NGA002579ABB Arctic communication solution ARM600 Vulnerabilities2025-04-07csaf · abb_psirtCH
ABB is aware of public reports of a vulnerabilities in product versions listed as affected in this advisory. An attacker who successfully exploited these vulnerabilities could cause the product to stop, make the product inacces-sible, take remote control of the product or insert and run arbitrary code. As part of ABB product lifecycle policy, once a product transitions to end-of-life, we discontinue maintenance, security patches, and technical support to focus on current and future technologies. While the product will continue to function, we strongly recommend implementing mitigations defined in this document, such as using a private APN cellular network between Arctic wireless gateways and ARM600 for establishing VPN tunnels, to mitigate security risks and avoid potential vulnerabilities. As part of ABB product lifecycle policy, once a product transitions to Limited state, we discontinue maintenance, security patches, and technical support to focus on current and future technologies. While the product will continue to function, we strongly recommend implementing mitigations defined in this document to mitigate security risks.
- RHSA-2022:6170Red Hat Security Advisory: rsync security update2022-08-24csaf · redhat_csafUS
An update for rsync is now available for Red Hat Enterprise Linux 7. Red Hat Product Security has rated this update as having a security impact of Important. 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.
- RHSA-2022:6171Red Hat Security Advisory: rsync security update2022-08-24csaf · redhat_csafUS
An update for rsync is now available for Red Hat Enterprise Linux 8.4 Extended Update Support. Red Hat Product Security has rated this update as having a security impact of Important. 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.
- RHSA-2022:6172Red Hat Security Advisory: rsync security update2022-08-24csaf · redhat_csafUS
An update for rsync is now available for Red Hat Enterprise Linux 8.2 Extended Update Support. Red Hat Product Security has rated this update as having a security impact of Important. 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.
- RHSA-2022:6173Red Hat Security Advisory: rsync security update2022-08-24csaf · redhat_csafUS
An update for rsync is now available for Red Hat Enterprise Linux 8.1 Update Services for SAP Solutions. Red Hat Product Security has rated this update as having a security impact of Important. 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.
- RHSA-2022:6180Red Hat Security Advisory: rsync security update2022-08-24csaf · redhat_csafUS
An update for rsync is now available for Red Hat Enterprise Linux 8. Red Hat Product Security has rated this update as having a security impact of Important. 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.
- RHSA-2022:6181Red Hat Security Advisory: rsync security update2022-08-24csaf · redhat_csafUS
An update for rsync is now available for Red Hat Enterprise Linux 9. Red Hat Product Security has rated this update as having a security impact of Important. 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-806742SSA-806742: Multiple Vulnerabilities in SCALANCE XCM-/XRM-300 before V2.42024-02-13csaf · siemens_psirtDE
SCALANCE XCM-/XRM-300 before V2.4 is affected by multiple vulnerabilities. Siemens has released an update for SCALANCE X-300 and recommends to update to the latest version.
- WID-SEC-W-2022-0891Rsync: Schwachstelle ermöglicht Manipulation von DateienDeutsch2022-08-02csaf · cert_bundDE
Ein entfernter, anonymer Angreifer kann eine Schwachstelle in Rsync ausnutzen, um Dateien zu manipulieren.
- WID-SEC-W-2023-0561Xerox FreeFlow Print Server: Mehrere SchwachstellenDeutsch2023-03-02csaf · cert_bundDE
Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Xerox FreeFlow Print Server ausnutzen, um die Vertraulichkeit, Verfügbarkeit und Integrität des Systems zu gefährden.
- WID-SEC-W-2023-0831IBM Security Verify Access: Mehrere SchwachstellenDeutsch2023-04-03csaf · cert_bundDE
Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in IBM Security Verify Access ausnutzen, um einen Cross-Site Scripting Angriff durchzuführen oder Daten zu manipulieren.
- WID-SEC-W-2023-1542Red Hat OpenShift: Mehrere SchwachstellenDeutsch2023-06-22csaf · cert_bundDE
Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Red Hat OpenShift ausnutzen, um einen Denial of Service Zustand herbeizuführen, Informationen offenzulegen, Dateien zu manipulieren oder Sicherheitsvorkehrungen zu umgehen.
- WID-SEC-W-2023-1969HPE Fabric OS: Mehrere Schwachstellen ermöglichen PrivilegieneskalationDeutsch2023-08-06csaf · cert_bundDE
Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in HPE Fabric OS für HPE Fibre Channel und SAN Switches ausnutzen, um seine Privilegien zu erhöhen, Informationen offenzulegen oder einen Denial of Service Zustand herbeizuführen.
- ICSA-24-046-11Siemens SCALANCE XCM-/XRM-3002024-02-13icsa · cisa_csaf_otUS
SCALANCE XCM-/XRM-300 before V2.4 is affected by multiple vulnerabilities. Siemens has released an update for SCALANCE X-300 and recommends to update to the latest version.
- ICSA-25-105-08ABB M2M Gateway2025-04-07icsa · cisa_csaf_otUS
ABB is aware of public reports of a vulnerabilities in product versions listed as affected in this advisory. An attacker who successfully exploited these vulnerabilities could cause the product to stop, make the product inacces-sible, take remote control of the product or insert and run arbitrary code. As part of ABB product lifecycle policy, once a product transitions to end-of-life, we discontinue maintenance, security patches, and technical support to focus on current and future technologies. While the product will continue to function, we strongly recommend implementing mitigations defined in this document, such as using a private APN cellular network between Arctic wireless gateways and ARM600 for establishing VPN tunnels, to mitigate security risks and avoid potential vulnerabilities. As part of ABB product lifecycle policy, once a product transitions to Limited state, we discontinue maintenance, security patches, and technical support to focus on current and future technologies. While the product will continue to function, we strongly recommend implementing mitigations defined in this document to mitigate security risks.
also known as (4)
Other names and identifiers for this entity.
sources
Which sources assert this record, and when.
references (49)
External citations — patches, advisories, analysis.
- http://www.openwall.com/lists/oss-security/2022/08/02/1cnnvd
- https://access.redhat.com/security/cve/cve-2022-29154cnnvd
- https://cxsecurity.com/cveshow/CVE-2022-29154/cnnvd
- https://github.com/WayneD/rsync/commit/b7231c7d02cfb65d291af74ff66e7d8c507ee871Patchcnnvd
- https://github.com/WayneD/rsync/tagscnnvd
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/NMBOJ77A7T7PQCARMDUK75TE6LLESZ3O/cnnvd
- https://lists.fedoraproject.org/archives/list/package-announce@lists.fedoraproject.org/message/YRQAI7H4M4RQZ2IWZUEEXECBE5D56BH2/cnnvd
- https://packetstormsecurity.com/files/168173/Red-Hat-Security-Advisory-2022-6170-01.htmlcnnvd
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan