An issue in wpa_supplicant all versions before v.2.12 allows a local attacker to bypass proper network context and AKMP matching for PMKSA caching via missing validation in the driver based PMKSA selection path in wpa.c
{
"binaries": [
{
"binary_name": "eapoltest",
"binary_version": "2:2.10-6ubuntu2.4"
},
{
"binary_name": "hostapd",
"binary_version": "2:2.10-6ubuntu2.4"
},
{
"binary_name": "wpagui",
"binary_version": "2:2.10-6ubuntu2.4"
},
{
"binary_name": "wpasupplicant",
"binary_version": "2:2.10-6ubuntu2.4"
}
]
}{
"binaries": [
{
"binary_name": "eapoltest",
"binary_version": "2:2.10-21ubuntu0.4"
},
{
"binary_name": "hostapd",
"binary_version": "2:2.10-21ubuntu0.4"
},
{
"binary_name": "wpagui",
"binary_version": "2:2.10-21ubuntu0.4"
},
{
"binary_name": "wpasupplicant",
"binary_version": "2:2.10-21ubuntu0.4"
}
]
}{
"binaries": [
{
"binary_name": "eapoltest",
"binary_version": "2:2.11-0ubuntu5"
},
{
"binary_name": "hostapd",
"binary_version": "2:2.11-0ubuntu5"
},
{
"binary_name": "wpagui",
"binary_version": "2:2.11-0ubuntu5"
},
{
"binary_name": "wpasupplicant",
"binary_version": "2:2.11-0ubuntu5"
}
]
}