| Summary: | roundcubemail new security issue CVE-2016-9920 | ||
|---|---|---|---|
| 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: | herman.viaene, lewyssmith, sysadmin-bugs |
| Version: | 5 | Keywords: | validated_update |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| URL: | https://lwn.net/Vulnerabilities/708655/ | ||
| Whiteboard: | MGA5-32-OK advisory MGA5-64-OK | ||
| Source RPM: | roundcubemail-1.0.9-1.mga5.src.rpm | CVE: | |
| Status comment: | |||
|
Description
David Walser
2016-12-09 18:19:20 CET
MGA5-32 on Acer D620 Xfce No installation issues. Still hitting same "Error 404" problem as in previous updates (bug 18257), so OK as is. CC:
(none) =>
herman.viaene
Lewis Smith
2016-12-28 10:54:53 CET
CC:
(none) =>
lewyssmith Testing M5 x64 All previous info got nowhere, so this is basically (as recommended) just an install + update run-through. BEFORE update: Installed from normal repos: roundcubemail-1.0.9-1.mga5 before I had set up a database - which threw an error "grep: /etc/php.d/99_apc.ini: No such file or directory ERROR: Error connecting to database: SQLSTATE[HY000] [1045] Access denied for user 'roundcube'@'localhost' (using password: YES)"; which I then did as per the Wiki: MariaDB [(none)]> CREATE USER roundcube IDENTIFIED BY 'pass'; MariaDB [(none)]> CREATE DATABASE roundcubemail; MariaDB [(none)]> GRANT ALL PRIVILEGES ON roundcubemail.* TO roundcube@localhost IDENTIFIED BY 'pass'; MariaDB [(none)]> FLUSH PRIVILEGES; MariaDB [(none)]> exit Using the example values means that /etc/roundcubemail/config.inc.php already has the correct database line: $config['db_dsnw'] = 'mysql://roundcube:pass@localhost/roundcubemail'; http://localhost/roundcubemail/ yielded a Roundcube page with "DATABASE ERROR: CONNECTION FAILED!" AFTER update to: roundcubemail-1.0.9-1.1.mga5 Two config file confirmations during the update (accepted both new). http://localhost/roundcubemail/ gave the same error as before. OKing this because the update went OK. But it would be nice to find a way to have this thing visibly working. Validating at the same time. Keywords:
(none) =>
validated_update An update for this issue has been pushed to the Mageia Updates repository. http://advisories.mageia.org/MGASA-2016-0430.html Status:
NEW =>
RESOLVED |