| Summary: | bip new security issue CVE-2013-4550 | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | David Walser <luigiwalser> |
| Component: | Security | Assignee: | QA Team <qa-bugs> |
| Status: | RESOLVED FIXED | QA Contact: | Sec team <security> |
| Severity: | normal | ||
| Priority: | Normal | CC: | sysadmin-bugs, tmb |
| Version: | 3 | Keywords: | validated_update |
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | Linux | ||
| URL: | http://lwn.net/Vulnerabilities/574573/ | ||
| Whiteboard: | MGA2TOO has_procedure advisory mga2-32-ok mga2-64-ok mga3-32-ok mga3-64-ok | ||
| Source RPM: | bip-0.8.8-11.mga3.src.rpm | CVE: | |
| Status comment: | |||
| Attachments: | bip.conf | ||
|
Description
David Walser
2013-11-21 16:40:13 CET
David Walser
2013-11-21 16:40:21 CET
Whiteboard:
(none) =>
MGA2TOO
David Walser
2013-11-21 16:42:32 CET
URL:
(none) =>
http://lwn.net/Vulnerabilities/574573/
claire robinson
2013-11-22 11:49:53 CET
Whiteboard:
MGA2TOO has_procedure =>
MGA2TOO has_procedure advisory Created attachment 4516 [details]
bip.conf
This is the bip.conf I'm using to test with. The login/password is mrsb/password on port 7778 and it'll join #mageia-qa as MrsBip2 so you might want to change those settings :)
When connecting to bip, for the server itself use the computer running bip and port 7778, then for the server password enter it as user:password:network In the attached conf mine would be mrsb:password:freenode Testing complete mga3 64 Whiteboard:
MGA2TOO has_procedure advisory =>
MGA2TOO has_procedure advisory mga3-64-ok Testing complete mga2 64 and mga3 32 Whiteboard:
MGA2TOO has_procedure advisory mga3-64-ok =>
MGA2TOO has_procedure advisory mga2-64-ok mga3-32-ok mga3-64-ok Testing complete mga2 32 Validating. Could sysadmin please push from 2&3 core/updates_testing to updates Thanks!
claire robinson
2013-11-22 13:31:04 CET
Keywords:
(none) =>
validated_update Update pushed: http://advisories.mageia.org/MGASA-2013-0351.html Status:
NEW =>
RESOLVED A second CVE was issued for another issue that was fixed with the same patch that fixed this issue. CVE-2011-5268 was also fixed here: http://openwall.com/lists/oss-security/2014/01/02/9 |