CVE-2021-43860 (from URL):
"Ryan Gonzalez discovered that Flatpak doesn't properly validate that the permissions displayed to the user for an app at install time match the actual permissions granted to the app at runtime, in the case that there's a null byte in the metadata file of an app. Therefore apps can grant themselves permissions without the consent of the user."
Fix in 1.10.6, 1.12.3.
The bug has been referenced in the following commit(s):
Author: Zac Medico <firstname.lastname@example.org>
AuthorDate: 2022-01-13 04:16:48 +0000
Commit: Zac Medico <email@example.com>
CommitDate: 2022-01-13 04:23:50 +0000
sys-apps/flatpak: Bump to version 1.10.6
Package-Manager: Portage-3.0.30, Repoman-3.0.3
Signed-off-by: Zac Medico <firstname.lastname@example.org>
sys-apps/flatpak/Manifest | 1 +
sys-apps/flatpak/flatpak-1.10.6.ebuild | 102 +++++++++++++++++++++++++++++++++
2 files changed, 103 insertions(+)
https://bugs.gentoo.org/8310#c4 too :)
Please stable when ready, thanks!
Flatpak is a Linux application sandboxing and distribution framework. A path traversal vulnerability affects versions of Flatpak prior to 1.12.3 and 1.10.6. flatpak-builder applies `finish-args` last in the build. At this point the build directory will have the full access that is specified in the manifest, so running `flatpak build` against it will gain those permissions. Normally this will not be done, so this is not problem. However, if `--mirror-screenshots-url` is specified, then flatpak-builder will launch `flatpak build --nofilesystem=host appstream-utils mirror-screenshots` after finalization, which can lead to issues even with the `--nofilesystem=host` protection. In normal use, the only issue is that these empty directories can be created wherever the user has write permissions. However, a malicious application could replace the `appstream-util` binary and potentially do something more hostile. This has been resolved in Flatpak 1.12.3 and 1.10.6 by changing the behaviour of `--nofilesystem=home` and `--nofilesystem=host`.