p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in flatpak

In den letzten 30 Tagen veröffentlichte Sicherheitslücken für flatpak: 0. Davon im KEV-Katalog: 0.

Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 2

  1. CVE-2024-42472

    Kritisch · CVSS 10EPSS 1,27%Korrektur verfügbar

    Flatpak may allow access to files outside sandbox for certain apps

    Flatpak is a Linux application sandboxing and distribution framework. Prior to versions 1.14.0 and 1.15.10, a malicious or compromised Flatpak app using persistent directories could access and write files outside of what it would otherwise have access to, which is an attack on integrity and confidentiality. When `persistent=subdir` is used in the application permissions (represented as `--persist=subdir` in the command-line interface), that means that an application which otherwise doesn't have access to the real user home directory will see an empty home directory with a writeable subdirectory `subdir`. Behind the scenes, this directory is

    • Auf 1.14.6-1ubuntu0.1 aktualisieren
    Veröffentlicht Aktualisiert
  2. CVE-2024-32462

    Hoch · CVSS 8.4EPSS 0,51%Korrektur verfügbar

    Flatpak vulnerable to a sandbox escape via RequestBackground portal due to bad argument parsing

    Flatpak is a system for building, distributing, and running sandboxed desktop applications on Linux. in versions before 1.10.9, 1.12.9, 1.14.6, and 1.15.8, a malicious or compromised Flatpak app could execute arbitrary code outside its sandbox. Normally, the `--command` argument of `flatpak run` expects to be given a command to run in the specified Flatpak app, optionally along with some arguments. However it is possible to instead pass `bwrap` arguments to `--command=`, such as `--bind`. It's possible to pass an arbitrary `commandline` to the portal interface `org.freedesktop.portal.Background.RequestBackground` from within a Flatpak app. Wh

    • Auf 1.14.6-1 aktualisieren
    Veröffentlicht Aktualisiert

Prüfen Sie Ihren Server

Gleichen Sie Ihren installierten Stack und seine Versionen mit den aktuellen Sicherheitsmeldungen ab.

Prüfen Sie Ihren Server →