oesa-2021-1043
Vulnerability from osv_openeuler
flatpak is a system for building, distributing and running sandboxed desktop applications on Linux. See https://wiki.gnome.org/Projects/SandboxedApps for more information.
Security Fix(es):
Flatpak is a system for building, distributing, and running sandboxed desktop applications on Linux. A bug was discovered in the flatpak-portal service that can allow sandboxed applications to execute arbitrary code on the host system (a sandbox escape). This sandbox-escape bug is present in versions from 0.11.4 and before fixed versions 1.8.5 and 1.9.4. The Flatpak portal D-Bus service (flatpak-portal, also known by its D-Bus service name org.freedesktop.portal.Flatpak) allows apps in a Flatpak sandbox to launch their own subprocesses in a new sandbox instance, either with the same security settings as the caller or with more restrictive security settings. For example, this is used in Flatpak-packaged web browsers such as Chromium to launch subprocesses that will process untrusted web content, and give those subprocesses a more restrictive sandbox than the browser itself. In vulnerable versions, the Flatpak portal service passes caller-specified environment variables to non-sandboxed processes on the host system, and in particular to the flatpak run command that is used to launch the new sandbox instance. A malicious or compromised Flatpak app could set environment variables that are trusted by the flatpak run command, and use them to execute arbitrary code that is not in a sandbox. As a workaround, this vulnerability can be mitigated by preventing the flatpak-portal service from starting, but that mitigation will prevent many Flatpak apps from working correctly. This is fixed in versions 1.8.5 and 1.9.4.(CVE-2021-21261)
| URL | Type | |
|---|---|---|
{
"affected": [
{
"ecosystem_specific": {
"aarch64": [
"flatpak-debugsource-1.0.3-3.oe1.aarch64.rpm",
"flatpak-debuginfo-1.0.3-3.oe1.aarch64.rpm",
"flatpak-devel-1.0.3-3.oe1.aarch64.rpm",
"flatpak-1.0.3-3.oe1.aarch64.rpm",
"flatpak-debugsource-1.0.3-3.oe1.aarch64.rpm",
"flatpak-debuginfo-1.0.3-3.oe1.aarch64.rpm",
"flatpak-devel-1.0.3-3.oe1.aarch64.rpm",
"flatpak-1.0.3-3.oe1.aarch64.rpm"
],
"noarch": [
"flatpak-help-1.0.3-3.oe1.noarch.rpm",
"flatpak-help-1.0.3-3.oe1.noarch.rpm"
],
"src": [
"flatpak-1.0.3-3.oe1.src.rpm",
"flatpak-1.0.3-3.oe1.src.rpm"
],
"x86_64": [
"flatpak-devel-1.0.3-3.oe1.x86_64.rpm",
"flatpak-debugsource-1.0.3-3.oe1.x86_64.rpm",
"flatpak-debuginfo-1.0.3-3.oe1.x86_64.rpm",
"flatpak-1.0.3-3.oe1.x86_64.rpm",
"flatpak-devel-1.0.3-3.oe1.x86_64.rpm",
"flatpak-debugsource-1.0.3-3.oe1.x86_64.rpm",
"flatpak-debuginfo-1.0.3-3.oe1.x86_64.rpm",
"flatpak-1.0.3-3.oe1.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:20.03-LTS",
"name": "flatpak",
"purl": "pkg:rpm/openEuler/flatpak\u0026distro=openEuler-20.03-LTS"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.0.3-3.oe1"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"ecosystem_specific": {
"aarch64": [
"flatpak-debugsource-1.0.3-3.oe1.aarch64.rpm",
"flatpak-debuginfo-1.0.3-3.oe1.aarch64.rpm",
"flatpak-devel-1.0.3-3.oe1.aarch64.rpm",
"flatpak-1.0.3-3.oe1.aarch64.rpm"
],
"noarch": [
"flatpak-help-1.0.3-3.oe1.noarch.rpm"
],
"src": [
"flatpak-1.0.3-3.oe1.src.rpm"
],
"x86_64": [
"flatpak-devel-1.0.3-3.oe1.x86_64.rpm",
"flatpak-debugsource-1.0.3-3.oe1.x86_64.rpm",
"flatpak-debuginfo-1.0.3-3.oe1.x86_64.rpm",
"flatpak-1.0.3-3.oe1.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:20.03-LTS-SP1",
"name": "flatpak",
"purl": "pkg:rpm/openEuler/flatpak\u0026distro=openEuler-20.03-LTS-SP1"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.0.3-3.oe1"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"database_specific": {
"severity": "High"
},
"details": "flatpak is a system for building, distributing and running sandboxed desktop applications on Linux. See https://wiki.gnome.org/Projects/SandboxedApps for more information.\r\n\r\nSecurity Fix(es):\r\n\r\nFlatpak is a system for building, distributing, and running sandboxed desktop applications on Linux. A bug was discovered in the `flatpak-portal` service that can allow sandboxed applications to execute arbitrary code on the host system (a sandbox escape). This sandbox-escape bug is present in versions from 0.11.4 and before fixed versions 1.8.5 and 1.9.4. The Flatpak portal D-Bus service (`flatpak-portal`, also known by its D-Bus service name `org.freedesktop.portal.Flatpak`) allows apps in a Flatpak sandbox to launch their own subprocesses in a new sandbox instance, either with the same security settings as the caller or with more restrictive security settings. For example, this is used in Flatpak-packaged web browsers such as Chromium to launch subprocesses that will process untrusted web content, and give those subprocesses a more restrictive sandbox than the browser itself. In vulnerable versions, the Flatpak portal service passes caller-specified environment variables to non-sandboxed processes on the host system, and in particular to the `flatpak run` command that is used to launch the new sandbox instance. A malicious or compromised Flatpak app could set environment variables that are trusted by the `flatpak run` command, and use them to execute arbitrary code that is not in a sandbox. As a workaround, this vulnerability can be mitigated by preventing the `flatpak-portal` service from starting, but that mitigation will prevent many Flatpak apps from working correctly. This is fixed in versions 1.8.5 and 1.9.4.(CVE-2021-21261)",
"id": "OESA-2021-1043",
"modified": "2026-08-06T11:04:16Z",
"published": "2021-03-05T11:04:16Z",
"references": [
{
"type": "ADVISORY",
"url": "https://openeuler.org/en/security/safety-bulletin/detail.html?id=openEuler-SA-2021-1043"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2021-21261"
}
],
"schema_version": "1.7.2",
"severity": [
{
"score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H",
"type": "CVSS_V3"
}
],
"summary": "flatpak security update",
"upstream": [
"CVE-2021-21261"
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.