Difference between revisions of "SVG:Advisory-SVG-CVE-2018-2562"
Jump to navigation
Jump to search
(Removed the "fix is not available", added more concrete SL link.) |
|||
Line 43: | Line 43: | ||
================================== | ================================== | ||
For RedHat see [R 2] | For RedHat see [R 2] | ||
For Ubuntu see [R 3] | For Ubuntu see [R 3] | ||
For Debian see [R 4] | For Debian see [R 4] | ||
For Scientific | For Scientific Linux see [R 5] | ||
Line 88: | Line 88: | ||
[R 4] https://security-tracker.debian.org/tracker/CVE-2018-2562 | [R 4] https://security-tracker.debian.org/tracker/CVE-2018-2562 | ||
[R 5] https://www.scientificlinux.org/ | [R 5] https://www.scientificlinux.org/?s=cve-2018-2562 | ||
[R 6] https://mariadb.com/kb/en/library/mariadb-10131-release-notes/ | [R 6] https://mariadb.com/kb/en/library/mariadb-10131-release-notes/ |
Latest revision as of 16:49, 23 October 2018
Main page | Software Security Checklist | Issue Handling | Advisories | Notes On Risk | Advisory Template | More |
Advisory-SVG-CVE-2018-2562
Title: EGI SVG 'ADVISORY' [TLP:WHITE] Up to 'HIGH' risk - MySQL server compromise [EGI-SVG-CVE-2018-2562] Date: 2018-04-13 Updated: Affected software and risk ========================== Up to HIGH risk vulnerability concerning MariaDB MySQL Package : MySQL CVE ID : CVE-2018-2562 This vulnerability allows low privileged attacker with network access via multiple protocols to compromise a MySQL Server Actions required/recommended ============================ Sites running MySQL should update if they are running distributions where a patch is available. If a patch is not available, sites should ensure that MySQL is not directly accessible on the network. Sites should always ensure that MySQL is not directly accessible from the network unless it is essential for that application. Affected software details ========================= This is fixed for MariaDB 10.1.31 and later [R 6], MariaDB 10.2.13 and later [R 7], MariaDB 5.5.59 and later[R 8] Mitigation ========== Ensure that MySQL is not directly exposed to the network. Component installation information ================================== For RedHat see [R 2] For Ubuntu see [R 3] For Debian see [R 4] For Scientific Linux see [R 5] TLP and URL =========== ** WHITE information - Unlimited distribution - see https://wiki.egi.eu/wiki/EGI_CSIRT:TLP for distribution restrictions*** URL: https://wiki.egi.eu/wiki/SVG:Advisory-SVG-CVE-2018-2562 Minor updates may be made without re-distribution to the sites Comments ======== Comments or questions should be sent to svg-rat at mailman.egi.eu If you find or become aware of another vulnerability which is relevant to EGI you may report it by e-mail to report-vulnerability at egi.eu the EGI Software Vulnerability Group will take a look according to the procedure defined in [R 9] Note that this has been updated and the latest version approved by the Operations Management Board in November 2017 References ========== [R 1] https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-2562 [R 2] https://access.redhat.com/security/cve/CVE-2018-2562 [R 3] http://people.canonical.com/~ubuntu-security/cve/2018/CVE-2018-2562.html [R 4] https://security-tracker.debian.org/tracker/CVE-2018-2562 [R 5] https://www.scientificlinux.org/?s=cve-2018-2562 [R 6] https://mariadb.com/kb/en/library/mariadb-10131-release-notes/ [R 7] https://mariadb.com/kb/en/library/mariadb-10213-release-notes/ [R 8] https://mariadb.com/kb/en/library/mariadb-5559-release-notes/ [R 9] https://documents.egi.eu/public/ShowDocument?docid=3145 Credit ====== SVG was alerted to this vulnerability by Mischa Salle Timeline ======== Yyyy-mm-dd [EGI-SVG-CVE-2018-2562] 2018-03-18 SVG alerted to this issue by Mischa Salle 2018-03-18 Acknowledgement from the EGI SVG to the reporter 2018-03-20 Investigation of vulnerability and relevance to EGI carried out 2018-03-20 EGI SVG Risk Assessment completed 2018-04--- Fix still not available for all linux distributions 2018-04-13 Advisory sent to sites Context ======= This advisory has been prepared as part of the effort to fulfil EGI SVG's purpose "To minimize the risk to the EGI infrastructure arising from software vulnerabilities" The risk is that assessed by the group, according to the EGI SVG issue handling procedure [R 9] in the context of how the software is used in the EGI infrastructure. It is the opinion of the group, we do not guarantee it to be correct. The risk may also be higher or lower in other deployments depending on how the software is used. Others may re-use this information provided they:- 1) Respect the provided TLP classification 2) Credit the EGI https://www.egi.eu/ Software Vulnerability Group