<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">On 21 September 2016 at 03:47, Zhixiong Chi <span dir="ltr"><<a href="mailto:Zhixiong.Chi@windriver.com" target="_blank">Zhixiong.Chi@windriver.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div id="gmail-:1pf" class="gmail-a3s gmail-aXjCH gmail-m1574aa4d6e7b1070">+From ecbb0b3dc122b0d290987cf9c84010<wbr>bbe53e1022 Mon Sep 17 00:00:00 2001<br>
+From: Jouni Malinen <<a href="mailto:jouni@qca.qualcomm.com">jouni@qca.qualcomm.com</a>><br>
+Date: Fri, 4 Mar 2016 17:20:18 +0200<br>
+Subject: [PATCH 1/2] WPS: Reject a Credential with invalid passphrase<br>
+<br>
+WPA/WPA2-Personal passphrase is not allowed to include control<br>
+characters. Reject a Credential received from a WPS Registrar both as<br>
+STA (Credential) and AP (AP Settings) if the credential is for WPAPSK or<br>
+WPA2PSK authentication type and includes an invalid passphrase.<br>
+<br>
+This fixes an issue where hostapd or wpa_supplicant could have updated<br>
+the configuration file PSK/passphrase parameter with arbitrary data from<br>
+an external device (Registrar) that may not be fully trusted. Should<br>
+such data include a newline character, the resulting configuration file<br>
+could become invalid and fail to be parsed.<br>
+<br>
+Upstream-Status: Backport<br>
+<br>
+Signed-off-by: Jouni Malinen <<a href="mailto:jouni@qca.qualcomm.com">jouni@qca.qualcomm.com</a>></div></blockquote></div><br>Please add your own s-o-b to the patch header, and as it fixes a CVE then a CVE tag (CVE: <span style="font-size:12.800000190734863px">CVE-2016-4476) too.</span></div><div class="gmail_extra"><span style="font-size:12.800000190734863px"><br></span></div><div class="gmail_extra"><span style="font-size:12.800000190734863px">Ross</span></div></div>