path: root/README
diff options
authorJouni Malinen <jouni@qca.qualcomm.com>2016-03-04 16:46:41 (GMT)
committerJouni Malinen <j@w1.fi>2016-05-02 08:08:25 (GMT)
commit73e4abb24a936014727924d8b0b2965edfc117dd (patch)
treefc41f67a4ae259cc0e5601177903dfb73f786892 /README
parentf529c0d9082b3ea4d165e4c74a9cb79f0498f204 (diff)
Reject psk parameter set with invalid passphrase character
WPA/WPA2-Personal passphrase is not allowed to include control characters. Reject a passphrase configuration attempt if that passphrase includes an invalid passphrase. This fixes an issue where wpa_supplicant could have updated the configuration file psk parameter with arbitrary data from the control interface or D-Bus interface. While those interfaces are supposed to be accessible only for trusted users/applications, it may be possible that an untrusted user has access to a management software component that does not validate the passphrase value before passing it to wpa_supplicant. This could allow such an untrusted user to inject up to 63 characters of almost arbitrary data into the configuration file. Such configuration file could result in wpa_supplicant trying to load a library (e.g., opensc_engine_path, pkcs11_engine_path, pkcs11_module_path, load_dynamic_eap) from user controlled location when starting again. This would allow code from that library to be executed under the wpa_supplicant process privileges. Signed-off-by: Jouni Malinen <jouni@qca.qualcomm.com>
Diffstat (limited to 'README')
0 files changed, 0 insertions, 0 deletions