{"answers":{"affected":"It affects 2 products.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-7303 exists.","fix":"Upgrade to a fixed version.","what":"CVE-2019-7303 is a medium-severity vulnerability in Canonical Ubuntu Linux, published on 23 Apr 2019. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2019-7303 and fix it if it is affected.\n\nWhat it is: CVE-2019-7303 is a medium-severity vulnerability in Canonical Ubuntu Linux, published on 23 Apr 2019. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2019-7303 exists.\n\nAffected product: Canonical Ubuntu Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2019-7303/ (Markdown: https://insights.sbomify.com/CVE-2019-7303/index.md)","id":"CVE-2019-7303","markdown":"https://insights.sbomify.com/CVE-2019-7303/index.md","name":"CVE-2019-7303","record":{"aliases":["DEBIAN-CVE-2019-7303","GHSA-hhhq-qgvm-w5hp","UBUNTU-CVE-2019-7303","USN-3917-1"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux package manager","requires_auth":"low_privilege","summary":"A flaw in snapd's seccomp filters allows strict mode snaps to bypass terminal restrictions and inject characters into the host terminal.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"canonical","cpe":[{"product":"snapd","vendor":"canonical"},{"product":"ubuntu_linux","vendor":"canonical"}],"cvss":{"score":5.7,"severity":"medium","source":"cna","vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L","version":"3.0"},"cwes":[{"id":"CWE-628","name":"Function Call with Incorrectly Specified Arguments"}],"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.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2019-03-22","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2019-03-22","kind":"exploitdb","ref":"46594","stars":null,"title":"snap - seccomp BBlacklist for TIOCSTI can be Circumvented"}],"tier":"weaponised"},"has_fix":true,"headline":"Snapd seccomp filter TIOCSTI ioctl bypass","id":"CVE-2019-7303","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"canonical:ubuntu_linux","products":["canonical:ubuntu_linux"],"type":"security_feature_bypass","year":"2019"},"n_packages":0,"n_references":2,"next":{"headline":"Local privilege escalation via snapd socket","id":"CVE-2019-7304"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2019-7301"},"products":["snapd"],"published":"2019-04-23","related":[{"cvss_score":10,"headline":"Command injection in snapd","id":"CVE-2023-1523","kev_date_added":null,"published":"2023-09-01"},{"cvss_score":9.3,"headline":"Privilege escalation in snapd","id":"CVE-2020-27352","kev_date_added":null,"published":"2024-06-21"},{"cvss_score":8.8,"headline":"Local privilege escalation via snapd socket","id":"CVE-2019-7304","kev_date_added":null,"published":"2019-04-23"},{"cvss_score":8.2,"headline":"snapd could be made to bypass intended access restrictions through snap content interfaces and layout paths","id":"CVE-2021-4120","kev_date_added":null,"published":"2022-02-17"},{"cvss_score":8.1,"headline":"CVE-2024-5138: snapd snapctl auth bypass","id":"CVE-2024-5138","kev_date_added":null,"published":"2024-05-31"},{"cvss_score":7.8,"headline":"snapd Race Condition vulnerability","id":"CVE-2022-3328","kev_date_added":null,"published":"2024-01-08"},{"cvss_score":7.8,"headline":"snapd could be made to escalate privileges and run programs as administrator","id":"CVE-2021-44730","kev_date_added":null,"published":"2022-02-17"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-17","vendors":["Canonical"]},"summary":"A flaw in snapd's seccomp filters allows strict mode snaps to bypass terminal restrictions and inject characters into the host terminal.","url":"https://insights.sbomify.com/CVE-2019-7303/"}