Skip to content
Fencer Intel
medium 5.7

CVE-2019-7303 json

Snapd seccomp filter TIOCSTI ioctl bypass

published 7y ago modified 4mo ago also EUVD-2019-16847

cvss
5.7
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
3.7%
EPSS 3.7% chance of exploitation in 30 days, percentile 89%
public exploits
1
Exploit-DB

Summary

A vulnerability in the seccomp filters of Canonical snapd before version 2.37.4 allows a strict mode snap to insert characters into a terminal on a 64-bit host. The seccomp rules were generated to match 64-bit ioctl(2) commands on a 64-bit platform; however, the Linux kernel only uses the lower 32 bits to determine which ioctl(2) commands to run. This issue affects: Canonical snapd versions prior to 2.37.4.

Patch / fix

  • Canonical snapd 2.37.4
  • snapd Debian 14, Debian 13, Debian 12 2.37.4-1

debian advisories DEBIAN-CVE-2019-7303

  • snapd Ubuntu 14.04 LTS 2.37.4~14.04.1
  • snapd Ubuntu 16.04 LTS 2.37.4ubuntu0.1
  • snapd Ubuntu 18.04 LTS 2.37.4+18.04.1

ubuntu advisories UBUNTU-CVE-2019-7303

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2019-7303 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

  1. First public exploit (EDB-46594)
  2. Published

Exploit prediction

3.70% chance of exploitation in the next 30 days, higher than 89% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • EDB-46594 snap - seccomp BBlacklist for TIOCSTI can be Circumvented dos, 2019-03-22

CVSS scores

assigned by version score vector
CNA 3.0 5.7 CVSS:3.0/AV:L/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:P/A:N

Affected products

  • Canonical snapd

Classification

Weakness
  • CWE-628 Function Call with Incorrectly Specified Arguments

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.