PyCryptodome and pycryptodomex before 3.19.1 allow side-channel leakage for OAEP decryption, exploitable for a Manger attack. https://github.com/Legrandin/pycryptodome/blob/master/Changelog.rst https://pypi.org/project/pycryptodomex/#history
Created 2ping tracking bugs for this issue: Affects: fedora-all [bug 2257030] Created pysnmp tracking bugs for this issue: Affects: openstack-rdo [bug 2257034]
pulp_container, and the dependency pyjwkest, seem to be perfectly compatible with pycryptodome 3.19.1+. Our upstream CI seems to currently use 3.20.0 with no issues Therefore, we can resolve this issue by simply upgrading the pycrytpodome package without needing any other code changes.
Thank you for confirming Daniel. We have now revised the impact of Satellite to Low and updated the corresponding statement.
This issue has been addressed in the following products: Red Hat Ansible Automation Platform 2.4 for RHEL 9 Red Hat Ansible Automation Platform 2.4 for RHEL 8 Via RHSA-2024:1057 https://access.redhat.com/errata/RHSA-2024:1057
This issue has been addressed in the following products: Red Hat Enterprise Linux 9.0 Extended Update Support Via RHSA-2024:1155 https://access.redhat.com/errata/RHSA-2024:1155
This issue has been addressed in the following products: Red Hat Satellite 6.15 for RHEL 8 Via RHSA-2024:2010 https://access.redhat.com/errata/RHSA-2024:2010
This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2024:2132 https://access.redhat.com/errata/RHSA-2024:2132
This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2024:2952 https://access.redhat.com/errata/RHSA-2024:2952
This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2024:2968 https://access.redhat.com/errata/RHSA-2024:2968