In words.protocols.jabber.xmlstream in Twisted through 19.2.1, XMPP support did not verify certificates when used with TLS, allowing an attacker to MITM connections. Upstream Issue: https://github.com/twisted/twisted/pull/1147
Created python-twisted tracking bugs for this issue: Affects: fedora-all [bug 1728207]
Marian, this seems a tad tricky to reproduce. Could you help to verify a fix?
https://src.fedoraproject.org/rpms/python-twisted/pull-request/8 https://koji.fedoraproject.org/koji/taskinfo?taskID=36150395
Sorry for the delay. I see you already have the fix?
I have a fix, but I don't know how to verify it.
Created python-twisted tracking bugs for this issue: Affects: openstack-rdo [bug 1740832]
python-twisted-19.2.1-3.fc30 has been pushed to the Fedora 30 stable repository. If problems still persist, please make note of it in this bug report.
Statement: * This issue affects the version of calamari-server(embeds python-twisted) as shipped with Red Hat Ceph Storage 2 as it does not check for TLS certificate. * This issue did not affect the versions of python-twisted-core as shipped with Red Hat Gluster Storage 3, Red Hat Ceph Storage 2 and 3 as it does not ship XMPP XML Stream bits. This issue affects the versions of python-twisted-words as shipped with Red Hat Enterprise Linux 6 and 7. Red Hat Enterprise Linux 6 is now in Maintenance Support 2 Phase of the support and maintenance life cycle. This has been rated as having a security impact of Moderate, and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat Enterprise Linux Life Cycle: https://access.redhat.com/support/policy/updates/errata/. Red Hat OpenStack Platform: * This flaw depends on the use of the XMPP protocol, which is not used in Red Hat OpenStack Platform. Although updating is recommended for affected versions, Red Hat OpenStack Platform environments are not vulnerable. Because of this and the lower product impact, no fixes will be issued for any Red Hat OpenStack Platform version at this time. * Because the flaw's impact is Low, it will not be fixed in Red Hat OpenStack Platform 9 which will retire shortly after the public date.