| Summary: | pcmanfm new security issue CVE-2017-8934 | ||
|---|---|---|---|
| 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: | brtians1, davidwhodgins, lewyssmith, nicolas.salguero, sysadmin-bugs |
| Version: | 5 | Keywords: | validated_update |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | advisory mga5-32-ok MGA5-64-OK | ||
| Source RPM: | pcmanfm-1.2.3-2.2.mga5.src.rpm | CVE: | CVE-2017-8934 |
| Status comment: | |||
|
Description
David Walser
2017-05-16 00:10:20 CEST
David Walser
2017-05-16 00:13:58 CEST
Whiteboard:
(none) =>
MGA5TOO Suggested advisory: ======================== The updated package fixes a security vulnerability: PCManFM 1.2.5 insecurely uses /tmp for a socket file, allowing a local user to cause a denial of service (application unavailability). (CVE-2017-8934) References: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-8934 http://openwall.com/lists/oss-security/2017/05/15/4 ======================== Updated packages in core/updates_testing: ======================== pcmanfm-1.2.3-2.3.mga5 from SRPMS: pcmanfm-1.2.3-2.3.mga5.src.rpm Source RPM:
pcmanfm-1.2.5-2.mga6.src.rpm =>
pcmanfm-1.2.3-2.2.mga5.src.rpm
Dave Hodgins
2017-05-21 03:02:10 CEST
Whiteboard:
(none) =>
advisory $ uname -a Linux localhost 4.4.68-desktop-1.mga5 #1 SMP Sun May 14 18:41:19 UTC 2017 i686 i686 i686 GNU/Linux running LXDE in vbox The following package is going to be installed: - pcmanfm-1.2.3-2.3.mga5.i586 110B of additional disk space will be used. 269KB of packages will be retrieved. Is it ok to continue? I opened it from the terminal and opened some files - it is working properly. opened via menu - tools - system tools - working as designed. CC:
(none) =>
brtians1 Testing M5_64, LXDE Updated pcmanfm to: pcmanfm-1.2.3-2.3.mga5 Tried various things from the menus as well as normal filesystem browsing. It seems to work as normal. OKing & validating; advisory already there. Keywords:
(none) =>
validated_update An update for this issue has been pushed to the Mageia Updates repository. http://advisories.mageia.org/MGASA-2017-0154.html Status:
ASSIGNED =>
RESOLVED |