{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-10145 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-10145 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-10145 is a high-severity vulnerability in [UNKNOWN] rkt, published on 3 Jun 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-10145 and fix it if it is affected.\n\nWhat it is: CVE-2019-10145 is a high-severity vulnerability in [UNKNOWN] rkt, published on 3 Jun 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: There is no known exploitation of CVE-2019-10145 in the wild and no public exploit code.\n\nAffected product: [UNKNOWN] rkt. 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-10145/ (Markdown: https://insights.sbomify.com/CVE-2019-10145/index.md)","id":"CVE-2019-10145","markdown":"https://insights.sbomify.com/CVE-2019-10145/index.md","name":"CVE-2019-10145","record":{"aliases":["GHSA-x384-w54q-v324","UBUNTU-CVE-2019-10145"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"patch","impacts":["privilege_escalation","data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"rkt container runtime","requires_auth":"none","summary":"Attackers can bypass seccomp filtering in rkt enter to access host resources from compromised containers, requiring a patch.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"rkt","vendor":"redhat"}],"cvss":{"score":7,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"},{"id":"CWE-250","name":"Execution with Unnecessary Privileges"}],"description":"rkt through version 1.30.0 does not isolate processes in containers that are run with `rkt enter`. Processes run with `rkt enter` do not have seccomp filtering during stage 2 (the actual environment in which the applications run). Compromised containers could exploit this flaw to access host resources.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Security feature bypass in rkt","id":"CVE-2019-10145","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2019"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site scripting in pki-core","id":"CVE-2019-10146"},"packages":[],"prev":{"headline":"Privilege escalation in rkt","id":"CVE-2019-10144"},"products":["rkt"],"published":"2019-06-03","related":[{"cvss_score":7,"headline":"Privilege escalation in rkt","id":"CVE-2019-10144","kev_date_added":null,"published":"2019-06-03"},{"cvss_score":4.7,"headline":"Privilege escalation in rkt","id":"CVE-2019-10147","kev_date_added":null,"published":"2019-06-03"}],"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)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["[UNKNOWN]"]},"summary":"Attackers can bypass seccomp filtering in rkt enter to access host resources from compromised containers, requiring a patch.","url":"https://insights.sbomify.com/CVE-2019-10145/"}