Bug 1542207 (CVE-2018-6560) - CVE-2018-6560 flatpak: sandbox escape in D-Bus filtering by a crafted authentication handshake
Summary: CVE-2018-6560 flatpak: sandbox escape in D-Bus filtering by a crafted authent...
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2018-6560
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1547003 1547376 1547377
Blocks: 1542208
TreeView+ depends on / blocked
 
Reported: 2018-02-05 20:21 UTC by Laura Pardo
Modified: 2019-09-29 14:31 UTC (History)
3 users (show)

Fixed In Version: flatpak 0.8.9, flatpak 0.10.3
Doc Type: If docs needed, set a value
Doc Text:
It was found that flatpak's D-Bus proxy did not properly filter the access to D-Bus during the authentication protocol. A specially crafted flatpak application could use this flaw to bypass all restrictions imposed by flatpak and have full access to the D-BUS interface.
Clone Of:
Environment:
Last Closed: 2019-06-08 03:39:19 UTC
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2018:2766 0 None None None 2018-09-25 19:07:07 UTC

Description Laura Pardo 2018-02-05 20:21:19 UTC 
A flaw was found in dbus-proxy/flatpak-proxy.c in Flatpak before 0.8.9, and 0.9.x and 0.10.x before 0.10.3, crafted. D-Bus messages to the host can be used to break out of the sandbox, because whitespace handling in the proxy is not identical to whitespace handling in the daemon.

References:
https://github.com/flatpak/flatpak/releases/tag/0.8.9
https://github.com/flatpak/flatpak/releases/tag/0.10.3

Patch:
https://github.com/flatpak/flatpak/commit/52346bf187b5a7f1c0fe9075b328b7ad6abe78f6
Comment 6 errata-xmlrpc 2018-09-25 19:07:01 UTC 
This issue has been addressed in the following products:

  Red Hat Enterprise Linux 7

Via RHSA-2018:2766 https://access.redhat.com/errata/RHSA-2018:2766
Note You need to log in before you can comment on or make changes to this bug.