CVE-2018-16359
First published: Sun Sep 02 2018(Updated: )
Google gVisor before 2018-08-23, within the seccomp sandbox, permits access to the renameat system call, which allows attackers to rename files on the host OS.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Google gVisor | <2018-08-23 |
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.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2018-16359?
CVE-2018-16359 has been classified as a medium severity vulnerability due to the potential for file renaming on the host OS.
How do I fix CVE-2018-16359?
To fix CVE-2018-16359, upgrade to Google gVisor version 2018-08-23 or later.
What systems are affected by CVE-2018-16359?
CVE-2018-16359 affects Google gVisor versions prior to 2018-08-23.
What type of attack can exploit CVE-2018-16359?
CVE-2018-16359 can be exploited by attackers to rename critical files on the host operating system.
Is CVE-2018-16359 part of the seccomp sandbox?
Yes, CVE-2018-16359 is a vulnerability within the seccomp sandbox of Google gVisor.
- collector/nvd-index
- agent/references
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/last-modified-date
- agent/author
- agent/description
- agent/first-publish-date
- agent/tags
- agent/event
- agent/source
- vendor/google
- canonical/google gvisor