More information about this security flaw is available in the following bug: http://bugzilla.redhat.com/show_bug.cgi?id=2282013 Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.
Use the following template to for the 'fedpkg update' request to submit an update for this issue as it contains the top-level parent bug(s) as well as this tracking bug. This will ensure that all associated bugs get updated when new packages are pushed to stable. ===== # bugfix, security, enhancement, newpackage (required) type=security # low, medium, high, urgent (required) severity=high # testing, stable request=testing # Bug numbers: 1234,9876 bugs=2282013,2293094 # Description of your update notes=Security fix for [PUT CVEs HERE] # Enable request automation based on the stable/unstable karma thresholds autokarma=True stable_karma=3 unstable_karma=-3 # Automatically close bugs when this marked as stable close_bugs=True # Suggest that users restart after update suggest_reboot=False ====== Additionally, you may opt to use the bodhi web interface to submit updates: https://bodhi.fedoraproject.org/updates/new
After some investigation, below is our conclusion of the analysis related to NetworkManager: - There are no relevant bits in NetworkManager - Both AP and client parts of the network association logic are handled by wpa_supplicant (or hostapd – same code base) - Users of NetworkManager as a Wi-Fi client can be affected, but fix needs to go to the wpa_supplicant and the infrastructure - Users of NetworkManager as a hot-spot are not affected because the attack needs multiple APs configured in a specific vulnerable fashion Therefore, closing as not a bug.