LiveActive security incident?Get immediate response
CVE Record

CVE-2019-7303: Snapd seccomp filter TIOCSTI ioctl bypass

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.

MediumCVSS 5.7Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2019-7303 is a sandbox escape weakness in Canonical snapd before 2.37.4. A confined snap could push characters into a user’s terminal on a 64-bit host, creating a local integrity and confidentiality risk. It requires local privileges and user interaction, so urgency is moderate unless untrusted snaps or shared systems are common.

Executive priority

Treat this as a moderate local containment failure. It is less urgent than remote code execution, but important for shared Linux environments, developer workstations, and systems where users may run third-party snaps. Patch during the next security maintenance window, faster for high-risk multi-user hosts.

Technical view

The issue is in snapd seccomp filtering for ioctl handling. Rules matched 64-bit ioctl command values, while the Linux kernel used only the lower 32 bits to select the ioctl operation. This allowed a strict mode snap to bypass the intended TIOCSTI restriction and inject terminal input on 64-bit systems.

Likely exposure

Exposure is likely on 64-bit Linux systems running Canonical snapd versions before 2.37.4, especially shared workstations, developer hosts, or environments allowing untrusted snaps. Systems without snapd or already updated to fixed vendor packages are not indicated as affected by the provided sources.

Exploitation context

The CVE is not listed as KEV in the provided bundle, so active exploitation is not established. A public Exploit-DB reference exists, indicating public exploit information was available. The vulnerability remains local and requires privileges plus user interaction, limiting broad remote attack potential.

Researcher notes

Key evidence is the CVE description and Ubuntu advisory: the bug depends on 64-bit ioctl filtering semantics versus kernel lower-32-bit ioctl selection. The provided sources do not establish active exploitation, affected distributions beyond Canonical snapd, or mitigations other than updating via vendor guidance.

Mitigation direction

  • Update Canonical snapd to version 2.37.4 or later.
  • Apply Ubuntu vendor updates referenced in USN-3917-1.
  • Prioritize shared hosts and systems allowing untrusted snap installation.
  • Review vendor guidance for distribution-specific fixed package versions.

Validation and detection

  • Inventory hosts with snapd installed and record package versions.
  • Confirm affected systems are updated beyond snapd 2.37.4.
  • Check whether local users can install or run untrusted strict mode snaps.
  • Verify Ubuntu security updates from USN-3917-1 are applied.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-628: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2019-7303 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.7 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/AV:L/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.7CVSS 3.0MediumCVSS:3.0/AV:L/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L1.53.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

5.7Medium
CVSS 3.0 vector shape for CVE-2019-7303Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/AV:L/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
CanonicalsnapdunspecifiedListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-628 · source CWE mapping

Function Call with Incorrectly Specified Arguments

Function Call with Incorrectly Specified Arguments represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.