Mark Chappell of Red Hat reports: When configured to automatically discover and store certificates the aes_security plugin relies on the file name of the SSL certificate as stored on the client rather than any of the information in the SSL certificate when creating the file to store the certificate in. Due to a lack of checks in aes_security.rb this allows arbitrary files to be created.
A planned disclosure date, Tuesday, July 15, 2014, at 14:30 UTC has been set, please note that this may change.
Created attachment 916998 [details] mcollective-2.5.2-flaw-in-aes_security.patch
Statement: Red Hat OpenShift Enterprise 2 is now in Production 1 Phase of the support and maintenance life cycle. This has been rated as having Moderate security impact and is not currently planned to be addressed in future updates. For additional information, refer to the Red Hat OpenShift Enterprise 2 Life Cycle: https://access.redhat.com/support/policy/updates/openshift.
Created mcollective tracking bugs for this issue: Affects: epel-5 [bug 1161821]
Created mcollective tracking bugs for this issue: Affects: epel-6 [bug 1161822]
Created mcollective tracking bugs for this issue: Affects: epel-7 [bug 1161823]
Created mcollective tracking bugs for this issue: Affects: fedora-all [bug 1161824]
Is it appropriate to go ahead and close the tracking bugs on this ticket?
It's wontfix for Red Hat, Fedora/EPEL may choose to rebase so we leave the trackers open for them.