{"push_id":1152300467,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"678db6ba60a3dc6665d99383e4e6ba2efd2ca2b7","before":"0f60f4dde2e0a38ad87d2ebb136adb83f113f370","commits":[{"sha":"678db6ba60a3dc6665d99383e4e6ba2efd2ca2b7","author":{"name":"Gustavo Zacarias","email":"c66b90184dd80a00a6f6ef8d0ff70881e786347b@zacarias.com.ar"},"message":"iperf3: security bump to version 3.1.3\n\nFixes:\nESNET-SECADV-2016-0001 - A malicious process can connect to an iperf3\nserver and, by sending a malformed message on the control channel,\ncorrupt the server process's heap area.  This can lead to a crash (and a\ndenial of service), or theoretically a remote code execution as the user\nrunning the iperf3 server. A malicious iperf3 server could potentially\nmount a similar attack on an iperf3 client.\n\nSigned-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>\nSigned-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>","distinct":true,"url":"https://api.github.com/repos/buildroot/buildroot/commits/678db6ba60a3dc6665d99383e4e6ba2efd2ca2b7"}]}
{"actor":{"display_login":"buildroot-auto-update"}}