REDHAT-BUG-667907: Low severity wpa_supplicant wpa_supplicant vulnerability
Enable the port when disabling countermeasures, and disable it on enabling countermeasures. This bug causes the response of the system to certain attacks to be ineffective. It also prevents wpasupplicant from getting scan results, as wpasupplicant disables countermeasures on startup - preventing the hardware from scanning. wpasupplicant works with apmode=2 despite this bug because the commit handler re-enables the port. The log tends to look like: State: DISCONNECTED -> SCANNING Starting AP scan for wildcard SSID Scan requested (ret=0) - scan timeout 5 seconds EAPOL: disable timer tick EAPOL: Supplicant port status: Unauthorized Scan timeout - try to get results Failed to get scan results Failed to get scan results - try scanning again Setting scan request: 1 sec 0 usec Starting AP scan for wildcard SSID Scan requested (ret=-1) - scan timeout 5 seconds Failed to initiate AP scan.
Upstream commit: http://git.kernel.org/linus/0a54917c3fc295cb61f3fb52373c173fd3b69f48
Affected Software
Event History
Frequently Asked Questions
What is the severity of REDHAT-BUG-667907?
REDHAT-BUG-667907 is classified as a significant issue affecting the response of the system to certain attacks.
How do I fix REDHAT-BUG-667907?
To mitigate REDHAT-BUG-667907, ensure that the port is enabled when disabling countermeasures and disabled when enabling countermeasures.
What software is affected by REDHAT-BUG-667907?
The vulnerability REDHAT-BUG-667907 specifically affects the wpa_supplicant software.
What issues does REDHAT-BUG-667907 cause?
REDHAT-BUG-667907 leads to ineffective attack responses and prevents wpa_supplicant from obtaining scan results.
Is there a known workaround for REDHAT-BUG-667907?
Currently, the only known approach to mitigate REDHAT-BUG-667907 is to manage the enabling and disabling of the port as specified.