Date: Thu, 25 May 2017 05:42:18 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 219521] databases/mysql56-server 2017Q2 branch still unpatched Message-ID: <bug-219521-13@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219521 Bug ID: 219521 Summary: databases/mysql56-server 2017Q2 branch still unpatched Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: Individual Port(s) Assignee: mmokhi@freebsd.org Reporter: danmcgrath.ca@gmail.com Assignee: mmokhi@freebsd.org Flags: maintainer-feedback?(mmokhi@freebsd.org) Just curious if MySQL 5.6 (mysql56-server-5.6.35_7) is ever going to be pat= ched for the latest round of CVE's? It's been like this for over a month now, I think? #> pkg audit mysql56-server-5.6.35_7 is vulnerable: MySQL -- mulitiple vulnerabilities CVE: CVE-2017-3468 CVE: CVE-2017-3467 CVE: CVE-2017-3465 CVE: CVE-2017-3464 CVE: CVE-2017-3461 CVE: CVE-2017-3462 CVE: CVE-2017-3463 CVE: CVE-2017-3459 CVE: CVE-2017-3457 CVE: CVE-2017-3458 CVE: CVE-2017-3456 CVE: CVE-2017-3460 CVE: CVE-2017-3305 CVE: CVE-2017-3455 CVE: CVE-2017-3454 CVE: CVE-2017-3452 CVE: CVE-2017-3453 CVE: CVE-2017-3331 CVE: CVE-2017-3600 CVE: CVE-2017-3329 CVE: CVE-2017-3599 CVE: CVE-2017-3450 CVE: CVE-2017-3309 CVE: CVE-2017-3308 WWW: https://vuxml.FreeBSD.org/freebsd/d9e01c35-2531-11e7-b291-b499baebfeaf.html --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-219521-13>