| Summary: | libuser new security issues CVE-2015-3245 and CVE-2015-3246 | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | David Walser <luigiwalser> |
| Component: | Security | Assignee: | QA Team <qa-bugs> |
| Status: | RESOLVED FIXED | QA Contact: | Sec team <security> |
| Severity: | critical | ||
| Priority: | Normal | CC: | davidwhodgins, marc.lattemann, ottoleipala1, peter.semiletov, sysadmin-bugs |
| Version: | 5 | Keywords: | validated_update |
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | Linux | ||
| URL: | http://lwn.net/Vulnerabilities/652362/ | ||
| Whiteboard: | MGA4TOO advisory MGA4-64-OK MGA5-32-OK | ||
| Source RPM: | libuser-0.60-5.mga5.src.rpm | CVE: | |
| Status comment: | |||
|
Description
David Walser
2015-07-23 20:40:55 CEST
David Walser
2015-07-23 20:41:53 CEST
Whiteboard:
(none) =>
MGA4TOO Advisory committed to svn. Testing shortly. CC:
(none) =>
davidwhodgins
David Walser
2015-07-24 17:15:51 CEST
URL:
(none) =>
http://lwn.net/Vulnerabilities/652362/ Sorry for the delay, had a power outage here, and fell asleep. Testing complete. Validating the update. Keywords:
(none) =>
validated_update An update for this issue has been pushed to Mageia Updates repository. http://advisories.mageia.org/MGASA-2015-0278.html Status:
NEW =>
RESOLVED Bug in just pushed libuser can't edit user groups from mcc or manatools. invalid content of lock /etc/shadow.lock I reopen this bug as we need to get where that bug is. Status:
RESOLVED =>
REOPENED Please open a new bug if there's a regression. Status:
REOPENED =>
RESOLVED (In reply to Otto Leipälä from comment #4) > Bug in just pushed libuser can't edit user groups from mcc or manatools. > invalid content of lock /etc/shadow.lock > I reopen this bug as we need to get where that bug is. It might require a reboot. As I did reboot between installing the update and testing, I'm not sure if it's needed or not. My /etc/shadow.lock file is empty ... # ll /etc/shadow.lock -rw------- 1 root root 0 May 21 2013 /etc/shadow.lock No i rebooted many times so there is real bug so don't close this yet. I can reproduce this error in mcc, which is gone by downgrading to previous version. However as suggest by David in Comment #5, we should open a new bug for it. CC:
(none) =>
marc.lattemann Don't need to create duplicate bug report please we can use same bug report to update and fix problem found from pushed update,as this releated to this exact package. (In reply to Otto Leipälä from comment #10) > Don't need to create duplicate bug report please we can use same bug report > to update and fix problem found from pushed update,as this releated to this > exact package. No, creating a new bug report is exactly what had to be done according to our policy. Once an update is pushed, its bug report is closed: the security issue has been fixed. If there are regressions, they need to be reported in another bug report to be fixed in another update. Yes you are right let this bug burried to six feet under and use that new one. This fix make Userdrake unstable - it can't normally create or delete the user. CC:
(none) =>
peter.semiletov (In reply to Peter Semiletov from comment #13) > This fix make Userdrake unstable - it can't normally create or delete the > user. Fix in progress, see bug 16467. |