From: Jouni Malinen Date: Sat, 2 May 2015 16:26:28 +0000 (+0300) Subject: EAP-pwd peer: Fix asymmetric fragmentation behavior X-Git-Tag: hostap_2_5~744 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=28a069a545b06b99eb55ad53f63f2c99e65a98f6;p=thirdparty%2Fhostap.git EAP-pwd peer: Fix asymmetric fragmentation behavior The L (Length) and M (More) flags needs to be cleared before deciding whether the locally generated response requires fragmentation. This fixes an issue where these flags from the server could have been invalid for the following message. In some cases, this could have resulted in triggering the wpabuf security check that would terminate the process due to invalid buffer allocation. Signed-off-by: Jouni Malinen --- diff --git a/src/eap_peer/eap_pwd.c b/src/eap_peer/eap_pwd.c index 1d2079b02..e58b13a42 100644 --- a/src/eap_peer/eap_pwd.c +++ b/src/eap_peer/eap_pwd.c @@ -968,6 +968,7 @@ eap_pwd_process(struct eap_sm *sm, void *priv, struct eap_method_ret *ret, /* * we have output! Do we need to fragment it? */ + lm_exch = EAP_PWD_GET_EXCHANGE(lm_exch); len = wpabuf_len(data->outbuf); if ((len + EAP_PWD_HDR_SIZE) > data->mtu) { resp = eap_msg_alloc(EAP_VENDOR_IETF, EAP_TYPE_PWD, data->mtu,