Debian LinuxOperating system · Debian
CVE-2019-8308
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedFlatpak before 1.0.7, and 1.1.x and 1.2.x before 1.2.3, exposes /proc in the apply_extra script sandbox, which allows attackers to modify a host-side executable file.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceFlatpak versions before 1.0.7 and before 1.2.3 expose the /proc filesystem within the apply_extra script sandbox, allowing a compromised or malicious application inside the sandbox to access and modify host-side executable files, enabling privilege escalation and host compromise.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Debian LinuxOperating system
= 9.0= 10.0
Enterprise Linux DesktopOperating system
= 7.0
Enterprise Linux ServerOperating system
= 7.0
Enterprise Linux Server AusOperating system
= 7.6
Enterprise Linux Server EusOperating system
= 7.6
Enterprise Linux Server TusOperating system
= 7.6
Enterprise Linux WorkstationOperating system
= 7.0< 1.0.7>= 1.1.0, <= 1.1.3>= 1.2.0, <= 1.2.3CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if Flatpak is installedRun `flatpak --version` or check for the flatpak binary at /usr/bin/flatpakAffected if Flatpak command returns a version number, meaning Flatpak is installed
-
Determine installed Flatpak versionRun `flatpak --version` and compare the output to the affected ranges: < 1.0.7, 1.1.0-1.1.3, or 1.2.0-1.2.3Affected if The version falls into any of these ranges: < 1.0.7, >= 1.1.0 AND <= 1.1.3, >= 1.2.0 AND <= 1.2.3
-
Identify if apply_extra scripts are in useSearch Flatpak manifest files (typically .json files) for the 'apply-extra' key, or examine Flatpak repositories for any configured apply_extra scripts using `flatpak info --app` on each installed applicationAffected if Any Flatpak application has an apply_extra script configured in its manifest
-
Check /proc exposure within Flatpak sandbox contextIf apply_extra scripts exist, inspect the sandbox configuration in the Flatpak manifest to verify if filesystem access allows /proc mounting or if the sandbox isolation is properly configuredAffected if The sandbox configuration permits /proc filesystem access or does not explicitly restrict it for applications with apply_extra scripts
You are affected if Flatpak is installed with a version in the ranges < 1.0.7, 1.1.0-1.1.3, or 1.2.0-1.2.3 AND you have any Flatpak applications using apply_extra scripts in your environment.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data1.0.7
Upgrade Flatpak to version 1.0.7, 1.2.3, or later. Ensure apply_extra scripts are only obtained from trusted sources and review existing Flatpak deployments for exposure.
Fix this in Debian Linux
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-8308 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-8308 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data