Bug 1099265 – VUL-0: CVE-2018-12559: cantata: Directory traversal due to insufficient mount target check in mounter.cpp

Bug 1099265 - (CVE-2018-12559) VUL-0: CVE-2018-12559: cantata: Directory traversal due to insufficient mount target check in mounter.cpp

(CVE-2018-12559)
Summary:	VUL-0: CVE-2018-12559: cantata: Directory traversal due to insufficient mount...

Status:	RESOLVED DUPLICATE of bug 1091824

Classification:	openSUSE
Product:	openSUSE Distribution
Classification:	openSUSE
Component:	Security
Version:	Leap 15.0
Hardware:	Other Other

Priority:	P5 - None Severity: Normal (vote)
Target Milestone:	---
Assigned To:	Cor Blom
QA Contact:	Security Team bot

URL:	https://smash.suse.de/issue/208462/
Whiteboard:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Create test case

Clone This Bug

Reported:	2018-06-27 09:03 UTC by Alexander Bergmann
Modified:	2018-06-27 11:11 UTC (History)
CC List:	0 users

See Also:
Found By:	Security Response Team
Services Priority:
Business Priority:
Blocker:	---
Marketing QA Status:	---
IT Deployment:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Alexander Bergmann 2018-06-27 09:03:51 UTC

rh#1595566

An issue was discovered in the cantata-mounter D-Bus service in Cantata through
2.3.1. The mount target path check in mounter.cpp `mpOk()` is insufficient. A
regular user can consequently mount a CIFS filesystem anywhere (e.g., outside of
the /home directory tree) by passing directory traversal sequences such as a
home/../usr substring.

References:
https://bugzilla.redhat.com/show_bug.cgi?id=1595566
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2018-12559
http://www.openwall.com/lists/oss-security/2018/06/18/1
http://people.canonical.com/~ubuntu-security/cve/2018/CVE-2018-12559.html
https://github.com/CDrummond/cantata/commit/afc4f8315d3e96574925fb530a7004cc9e6ce3d3

Comment 1 Cor Blom 2018-06-27 11:11:44 UTC

We don't build with this option.

*** This bug has been marked as a duplicate of bug 1091824 ***