This is an automatically created tracking bug! It was created to ensure that one or more security vulnerabilities are fixed in affected versions of Fedora. For comments that are specific to the vulnerability please use bugs filed against the "Security Response" product referenced in the "Blocks" field. For more information see: http://fedoraproject.org/wiki/Security/TrackingBugs When submitting as an update, use the fedpkg template provided in the next comment(s). This will include the bug IDs of this tracking bug as well as the relevant top-level CVE bugs. Please also mention the CVE IDs being fixed in the RPM changelog and the fedpkg commit message. NOTE: this issue affects multiple supported versions of Fedora. While only one tracking bug has been filed, please correct all affected versions at the same time. If you need to fix the versions independent of each other, you may clone this bug as appropriate. [bug automatically created by: add-tracking-bugs]
Use the following template to for the 'fedpkg update' request to submit an update for this issue as it contains the top-level parent bug(s) as well as this tracking bug. This will ensure that all associated bugs get updated when new packages are pushed to stable. ===== # bugfix, security, enhancement, newpackage (required) type=security # testing, stable request=testing # Bug numbers: 1234,9876 bugs=1443358,1443359,1443360,1443365,1443369,1443376,1443377,1443378,1443379,1443387,1443408 # Description of your update notes=Security fix for CVE-2017-3308, CVE-2017-3309, CVE-2017-3329, CVE-2017-3453, CVE-2017-3456, CVE-2017-3461, CVE-2017-3462, CVE-2017-3463, CVE-2017-3464, CVE-2017-3600 # Enable request automation based on the stable/unstable karma thresholds autokarma=True stable_karma=3 unstable_karma=-3 # Automatically close bugs when this marked as stable close_bugs=True # Suggest that users restart after update suggest_reboot=False ====== Additionally, you may opt to use the bodhi web interface to submit updates: https://bodhi.fedoraproject.org/updates/new
Fixed in 10.1.23 (current version is 10.1.24): CVE-2017-3308 CVE-2017-3309 CVE-2017-3453 CVE-2017-3456 CVE-2017-3464 Not fixed yet: CVE-2017-3461 CVE-2017-3462 CVE-2017-3463 Source: https://mariadb.com/kb/en/mariadb/security/
Tomas, can you please check, that those 3 CVE's left are really applicable to MDB >=10.1.26 in Fedora <= F26 MDB >=10.2.8 in Fedora >= F27 This tracker bug is few months old, and upstream does not seem to plan to fix those CVE's. But if they are applicable, I'll reach upstream, ask them, if they know about them and I'll bring some fix.
According to the following page: https://mariadb.com/kb/en/the-mariadb-library/security-vulnerabilities-in-oracle-mysql-that-did-not-exist-in-mariadb/#httpwwworaclecomtechnetworksecurity-advisorycpuapr2017-3236618htmlapril-2017 MariaDB upstream does not believe CVE-2017-3461/2/3 were applicable to MariaDB.
Good, thank you. In that case, everything fixed !