CVE-2019-7303
CVE-2019-7303 is a high-severity vulnerability in Canonical Snapd with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-628.
Key facts
- Severity: High (CVSS 3.x base score 7.5)
- CVSS v2: 5.0
- EPSS exploit prediction: 4% (88th percentile)
- Actively exploited: Not listed in CISA KEV
- Weakness: CWE-628
- Affected product: Canonical Snapd
- Published:
- Last modified:
Description
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.
Frequently asked questions
- What is CVE-2019-7303?
- 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.
- How severe is CVE-2019-7303?
- CVE-2019-7303 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity high, and availability none.
- Is CVE-2019-7303 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 4% (88th percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2019-7303?
- CVE-2019-7303 primarily affects Canonical Snapd. In total, 5 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
- How do I fix CVE-2019-7303?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
- When was CVE-2019-7303 published?
- CVE-2019-7303 was published on 2019-04-23 and last updated on 2026-06-17.
References
Affected products (5)
- cpe:2.3:a:canonical:snapd:*:*:*:*:*:*:*:*
- cpe:2.3:o:canonical:ubuntu_linux:14.04:*:*:*:lts:*:*:*
- cpe:2.3:o:canonical:ubuntu_linux:16.04:*:*:*:lts:*:*:*
- cpe:2.3:o:canonical:ubuntu_linux:18.04:*:*:*:lts:*:*:*
- cpe:2.3:o:canonical:ubuntu_linux:18.10:*:*:*:*:*:*:*
More vulnerabilities in Canonical Snapd
- CVE-2023-1523 — Critical (CVSS 10.0): Using the TIOCLINUX ioctl request, a malicious snap could inject contents into the input of the controlling terminal…
- CVE-2019-7304 — Critical (CVSS 9.8): Canonical snapd before version 2.37.1 incorrectly performed socket owner validation, allowing an attacker to run…
- CVE-2020-27352 — Critical (CVSS 9.3): When generating the systemd service units for the docker snap (and other similar snaps), snapd does not specify…
- CVE-2021-4120 — High (CVSS 8.2): snapd 2.54.2 fails to perform sufficient validation of snap content interface and layout paths, resulting in the…
- CVE-2024-5138 — High (CVSS 8.1): The snapctl component within snapd allows a confined snap to interact with the snapd daemon to take certain privileged…
- CVE-2022-3328 — High (CVSS 7.8): Race condition in snap-confine's must_mkdir_and_open_with_perms()
All CVEs affecting Canonical Snapd →
Other CWE-628 vulnerabilities
- CVE-2026-43133 — High (CVSS 7.9): In the Linux kernel, the following vulnerability has been resolved: KVM: nSVM: Always use vmcb01 in VMLOAD/VMSAVE…
- CVE-2019-14844 — High (CVSS 7.5): A flaw was found in, Fedora versions of krb5 from 1.16.1 to, including 1.17.x, in the way a Kerberos client could crash…
- CVE-2025-0325 — Medium (CVSS 4.3): A Guard Tour VAPIX API parameter allowed the use of arbitrary values and can be incorrectly called, allowing an…