{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-20168 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-20168 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-20168 is a medium-severity denial of service vulnerability in n/a, published on 17 Dec 2018. 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-2018-20168 and fix it if it is affected.\n\nWhat it is: CVE-2018-20168 is a medium-severity denial of service vulnerability in n/a, published on 17 Dec 2018. 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-2018-20168 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2018-20168/ (Markdown: https://insights.sbomify.com/CVE-2018-20168/index.md)","id":"CVE-2018-20168","markdown":"https://insights.sbomify.com/CVE-2018-20168/index.md","name":"CVE-2018-20168","record":{"aliases":["GHSA-7rr2-q546-7grq"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"gVisor container runtime","requires_auth":"none","summary":"Attackers can cause a denial of service in gVisor via a crafted application due to improper pagetable reuse, requiring an upgrade to fix.","user_interaction":"required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"gvisor","vendor":"google"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H","version":"3.0"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"Google gVisor before 2018-08-22 reuses a pagetable in a different level with the paging-structure cache intact, which allows attackers to cause a denial of service (\"physical address not valid\" panic) via a crafted application.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Denial of service in n/a","id":"CVE-2018-20168","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2018"},"n_packages":0,"n_references":1,"next":{"headline":"Denial of service in n/a","id":"CVE-2018-20169"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2018-20167"},"products":["n/a"],"published":"2018-12-17","related":[{"cvss_score":9.8,"headline":"Use after free in n/a","id":"CVE-2018-19333","kev_date_added":null,"published":"2018-11-17"},{"cvss_score":6.8,"headline":"Improper File Permission Handling in Google gVisor runsc","id":"CVE-2025-2713","kev_date_added":null,"published":"2025-03-28"},{"cvss_score":6.8,"headline":"Path traversal in n/a","id":"CVE-2018-16359","kev_date_added":null,"published":"2018-09-02"},{"cvss_score":6.3,"headline":"Improved Seeding and Hashing In gVisor","id":"CVE-2024-10026","kev_date_added":null,"published":"2025-01-30"},{"cvss_score":6.3,"headline":"Information disclosure in gVisor","id":"CVE-2024-10603","kev_date_added":null,"published":"2025-01-30"},{"cvss_score":4.8,"headline":"Denial-of-Service in Gvisor","id":"CVE-2023-7258","kev_date_added":null,"published":"2024-05-15"}],"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-05","vendors":["n/a"]},"summary":"Attackers can cause a denial of service in gVisor via a crafted application due to improper pagetable reuse, requiring an upgrade to fix.","url":"https://insights.sbomify.com/CVE-2018-20168/"}