| Summary: | Multiple vulnerabilities in mariadb/mysql (CVE-2013-3783, 3793, 3794, 3795, 3796, 3798, 3801, 3802, 3804, 3805, 3806, 3807, 3808, 3809, 3810, 3811, 3812) | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Oden Eriksson <oe> |
| Component: | Security | Assignee: | AL13N <alien> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Sec team <security> |
| Severity: | normal | ||
| Priority: | Normal | CC: | alien, luigiwalser, tmb |
| Version: | 2 | ||
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | mariadb | CVE: | |
| Status comment: | |||
|
Description
Oden Eriksson
2013-07-23 07:44:40 CEST
Oden Eriksson
2013-07-23 08:16:56 CEST
Source RPM:
mysql =>
mariadb
Oden Eriksson
2013-07-23 08:17:19 CEST
Summary:
Multiple vulnerabilities in mysql (CVE-2013-3783, 3793, 3794, 3795, 3796, 3798, 3801, 3802, 3804, 3805, 3806, 3807, 3808, 3809, 3810, 3811, 3812) =>
Multiple vulnerabilities in mariadb/mysql (CVE-2013-3783, 3793, 3794, 3795, 3796, 3798, 3801, 3802, 3804, 3805, 3806, 3807, 3808, 3809, 3810, 3811, 3812) and mariadb piggy-backs on mysql, no? Yep... CC:
(none) =>
tmb Duplicate. *** This bug has been marked as a duplicate of bug 9878 *** Status:
NEW =>
RESOLVED I think you're mistaking closing this bug as it affects mga2 and mga3 as far as I can tell. mariadb-5.5.32-1.mga3 was submitted to core/updates_testing yesterday, but I'm awating information how these CVE's affects mariadb. Status:
RESOLVED =>
REOPENED The other bug is for Mageia 2 and 3. *** This bug has been marked as a duplicate of bug 9878 *** Status:
REOPENED =>
RESOLVED Please note the way we handle a bug for multiple versions using the whiteboard. We always set the version to the *highest* version affected, and then add tags in the whiteboard for other versions affected. So, for a bug affecting Cauldron, Mageia 3, and Mageia 2, the whiteboard has: MGA3TOO, MGA2TOO For a bug just affecting Mageia 2 and Mageia 3, version is 3, whiteboard has: MGA2TOO well, that was just it... this isn't resolved in cauldron and for cauldron it could take a while... even mga3 isn't fixed imho, not even if it would be validated... it needs more checking and some CVE explanations to be sure Indeed. We normally try to have things fixed in Cauldron before shipping updates for stable. If we can't do that this time, we will need a new bug for QA, so I suppose we could use this one for that. Let's wait to reopen it until there are update candidates ready :o) cauldron can't be fixed for now (could take a while) the one in mga3 was submitted, even though it needs some checking |