CVE-2018-19333
First published: Sat Nov 17 2018(Updated: )
pkg/sentry/kernel/shm/shm.go in Google gVisor before 2018-11-01 allows attackers to overwrite memory locations in processes running as root (but not escape the sandbox) via vectors involving IPC_RMID shmctl calls, because reference counting is mishandled.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Google gVisor | <2018-11-01 |
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-19333?
CVE-2018-19333 is considered a high-severity vulnerability due to its potential to allow attackers to overwrite memory in processes running as root.
How do I fix CVE-2018-19333?
To fix CVE-2018-19333, update Google gVisor to version 2018-11-01 or later.
What systems are affected by CVE-2018-19333?
CVE-2018-19333 affects Google gVisor versions prior to 2018-11-01.
Can CVE-2018-19333 allow attackers to escape the gVisor sandbox?
No, CVE-2018-19333 does not allow attackers to escape the gVisor sandbox, but it does pose a risk of memory overwrite.
In which component of gVisor is CVE-2018-19333 found?
CVE-2018-19333 is found in the pkg/sentry/kernel/shm/shm.go component of Google gVisor.
- collector/nvd-index
- agent/references
- agent/type
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/author
- agent/last-modified-date
- agent/severity
- agent/remedy
- agent/tags
- agent/description
- agent/first-publish-date
- agent/event
- agent/source
- vendor/google
- canonical/google gvisor