CVE-2017-5226
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 · uneditedWhen executing a program via the bubblewrap sandbox, the nonpriv session can escape to the parent session by using the TIOCSTI ioctl to push characters into the terminal's input buffer, allowing an attacker to escape the sandbox.
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 confidenceBubblewrap sandbox fails to restrict the TIOCSTI ioctl, allowing a confined process to inject characters into the terminal's input buffer and escape to the parent session by simulating keystrokes that execute commands outside the sandbox.
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<= 0.1.5CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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.
-
Verify bubblewrap is installedRun 'which bubblewrap' or check your package manager for bubblewrapAffected if bubblewrap is not installed on the system
-
Determine installed bubblewrap versionRun 'bubblewrap --version' or check via package manager (rpm -q bubblewrap, dpkg -l bubblewrap)Affected if the version command fails or bubblewrap is not found
-
Compare version against affected rangeCompare the installed version number to the affected range: versions 0.1.5 and earlierAffected if the installed version is 0.1.5 or lower
-
Check seccomp-bpf policy configuration (optional)Inspect the bubblewrap source code or seccomp policy file for TIOCSTI ioctl filtering rulesAffected if the policy does not explicitly block or deny the TIOCSTI syscall
You are affected if bubblewrap is installed with version 0.1.5 or lower and the seccomp-bpf policy does not filter the TIOCSTI ioctl syscall.
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.
dbcve · scopedApply the upstream patch that filters or denies the TIOCSTI ioctl syscall within the bubblewrap seccomp-bpf policy to prevent terminal input buffer manipulation.
Bubblewrap >= 0.1.6
- 1. Identify the current Bubblewrap version installed (e.g., `bwrap --version` or via package manager)
- 2. Upgrade Bubblewrap to version 0.1.6 or later which contains the fix for the TIOCSTI ioctl sandbox escape
- 3. If using a distribution package manager (apt, yum, dnf), update the package: `apt-get update && apt-get install bubblewrap` or `dnf update bubblewrap`
- 4. If building from source, obtain version 0.1.6 or later from the upstream repository
- 5. Verify the upgrade was successful by checking the version number
- 6. Test that bubblewrap still functions correctly with your intended use cases
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-5226 — 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-2017-5226 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