Lookup for vulnerable packages by Package URL.
| Purl | pkg:apk/alpine/flatpak@1.12.3-r0?arch=x86&distroversion=v3.20&reponame=community |
|---|
| Type | apk |
|---|
| Namespace | alpine |
|---|
| Name | flatpak |
|---|
| Version | 1.12.3-r0 |
|---|
| Qualifiers |
| arch |
x86 |
| distroversion |
v3.20 |
| reponame |
community |
|
|---|
| Subpath | |
|---|
| Is_vulnerable | false |
|---|
| Next_non_vulnerable_version | 1.12.5-r0 |
|---|
| Latest_non_vulnerable_version | 1.14.10-r0 |
|---|
| Affected_by_vulnerabilities |
|
|---|
| Fixing_vulnerabilities |
| 0 |
| url |
VCID-rpqr-5dz5-qqam |
| vulnerability_id |
VCID-rpqr-5dz5-qqam |
| summary |
Flatpak is a Linux application sandboxing and distribution framework. Prior to versions 1.12.3 and 1.10.6, 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. Flatpak shows permissions to the user during install by reading them from the "xa.metadata" key in the commit metadata. This cannot contain a null terminator, because it is an untrusted GVariant. Flatpak compares these permissions to the *actual* metadata, from the "metadata" file to ensure it wasn't lied to. However, the actual metadata contents are loaded in several places where they are read as simple C-style strings. That means that, if the metadata file includes a null terminator, only the content of the file from *before* the terminator gets compared to xa.metadata. Thus, any permissions that appear in the metadata file after a null terminator are applied at runtime but not shown to the user. So maliciously crafted apps can give themselves hidden permissions. Users who have Flatpaks installed from untrusted sources are at risk in case the Flatpak has a maliciously crafted metadata file, either initially or in an update. This issue is patched in versions 1.12.3 and 1.10.6. As a workaround, users can manually check the permissions of installed apps by checking the metadata file or the xa.metadata key on the commit metadata. |
| references |
| 0 |
|
| 1 |
| reference_url |
https://api.first.org/data/v1/epss?cve=CVE-2021-43860 |
| reference_id |
|
| reference_type |
|
| scores |
| 0 |
| value |
0.00166 |
| scoring_system |
epss |
| scoring_elements |
0.37337 |
| published_at |
2026-06-04T12:55:00Z |
|
| 1 |
| value |
0.00166 |
| scoring_system |
epss |
| scoring_elements |
0.37428 |
| published_at |
2026-06-05T12:55:00Z |
|
| 2 |
| value |
0.00166 |
| scoring_system |
epss |
| scoring_elements |
0.37433 |
| published_at |
2026-06-06T12:55:00Z |
|
| 3 |
| value |
0.00166 |
| scoring_system |
epss |
| scoring_elements |
0.37401 |
| published_at |
2026-06-07T12:55:00Z |
|
| 4 |
| value |
0.00166 |
| scoring_system |
epss |
| scoring_elements |
0.37362 |
| published_at |
2026-06-08T12:55:00Z |
|
| 5 |
| value |
0.00166 |
| scoring_system |
epss |
| scoring_elements |
0.37375 |
| published_at |
2026-06-09T12:55:00Z |
|
|
| url |
https://api.first.org/data/v1/epss?cve=CVE-2021-43860 |
|
| 2 |
|
| 3 |
|
| 4 |
|
| 5 |
|
| 6 |
|
| 7 |
|
|
| fixed_packages |
|
| aliases |
CVE-2021-43860
|
| risk_score |
3.7 |
| exploitability |
0.5 |
| weighted_severity |
7.4 |
| resource_url |
http://public2.vulnerablecode.io/vulnerabilities/VCID-rpqr-5dz5-qqam |
|
|
|---|
| Risk_score | null |
|---|
| Resource_url | http://public2.vulnerablecode.io/packages/pkg:apk/alpine/flatpak@1.12.3-r0%3Farch=x86&distroversion=v3.20&reponame=community |
|---|