Update for CVE-2021-21381
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
flatpak (Debian) |
Fix Released
|
Unknown
|
|||
flatpak (Ubuntu) |
Fix Released
|
Medium
|
Andrew Hayzen | ||
Bionic |
Fix Released
|
Medium
|
Steve Beattie | ||
Focal |
Fix Released
|
Medium
|
Steve Beattie | ||
Groovy |
Fix Released
|
Medium
|
Steve Beattie |
Bug Description
[Links]
https:/
https:/
https:/
https:/
[Impact]
Versions in Ubuntu right now:
Hirsute: 1.10.1-4
Groovy: 1.8.2-1ubuntu0.1
Focal: 1.6.5-0ubuntu0.2
Bionic: 1.0.9-0ubuntu0.2
Affected versions:
>= 0.9.4
Patched versions:
>= 1.10.2
[Test Case]
No test case has been mentioned yet, but in the patches there are changes/additions to the unit tests.
[Regression Potential]
Flatpak has a test suite, which is run on build across all relevant architectures and passes.
There is also a manual test plan https:/
Flatpak has autopkgtests enabled http://
Regression potential is low, and upstream is very responsive to any issues raised.
[Other information]
Sandbox escape via special tokens in .desktop file (flatpak#4146)
Flatpak since 0.9.4 has a vulnerability in the "file forwarding" feature which can be used by an attacker to gain access to files that would not ordinarily be allowed by the app's permissions.
Impact
By putting the special tokens @@ and/or @@u in the Exec field of a Flatpak app's .desktop file, a malicious app publisher can trick flatpak into behaving as though the user had chosen to open a target file with their Flatpak app, which automatically makes that file available to the Flatpak app.
A minimal solution is the first commit "Disallow @@ and @@U usage in desktop files". The follow-up commits "dir: Reserve the whole @@ prefix" and "dir: Refuse to export .desktop files with suspicious uses of @@ tokens" are recommended, but not strictly required.
Workarounds
Avoid installing Flatpak apps from untrusted sources, or check the contents of the exported .desktop files in exports/
References
Acknowledgements
Thanks to @AntonLydike for reporting this issue, and @refi64 for providing the initial solution.
CVE References
Changed in flatpak (Ubuntu): | |
assignee: | nobody → Andrew Hayzen (ahayzen) |
status: | New → In Progress |
description: | updated |
Changed in flatpak (Ubuntu): | |
importance: | Undecided → High |
Changed in flatpak (Ubuntu Bionic): | |
importance: | Undecided → High |
Changed in flatpak (Ubuntu Focal): | |
importance: | Undecided → High |
Changed in flatpak (Ubuntu Groovy): | |
importance: | Undecided → High |
Changed in flatpak (Debian): | |
status: | Unknown → Fix Released |
Changed in flatpak (Ubuntu Bionic): | |
importance: | High → Medium |
Changed in flatpak (Ubuntu Focal): | |
importance: | High → Medium |
Changed in flatpak (Ubuntu Groovy): | |
importance: | High → Medium |
Changed in flatpak (Ubuntu): | |
importance: | High → Medium |
summary: |
- Update for GHSA-xgh4-387p-hqpp + Update for CVE-2021-21381 |
This is the bionic debdiff.