CVE-2018-20168: Input Validation
First published: Mon Dec 17 2018(Updated: )
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.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Google gVisor | <2018-08-22 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Frequently Asked Questions
What is the severity of CVE-2018-20168?
CVE-2018-20168 is classified as a denial of service vulnerability.
How do I fix CVE-2018-20168?
To mitigate CVE-2018-20168, update Google gVisor to version 2018-08-22 or later.
What impact does CVE-2018-20168 have?
CVE-2018-20168 can cause a denial of service by raising a 'physical address not valid' panic.
Which versions of gVisor are affected by CVE-2018-20168?
CVE-2018-20168 affects Google gVisor versions before 2018-08-22.
Who is affected by CVE-2018-20168?
Users running vulnerable versions of Google gVisor may experience service disruptions.
- collector/nvd-index
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/severity
- agent/references
- agent/remedy
- agent/author
- agent/weakness
- agent/first-publish-date
- agent/event
- agent/description
- agent/tags
- agent/source
- vendor/google
- canonical/google gvisor