Brian May <[email protected]> writes: > I just had a look at CVE-2016-6830.
I was going to look at CVE-2016-6831 seperately, however it looks like this was fixed at the same time as CVE-2016-6830 http://seclists.org/oss-sec/2016/q3/308 -- Brian May <[email protected]>
