Google Gvisor
7 CVEs affecting Google Gvisor. Latest disclosed: 2025-03-28. Critical: 1, High: 1.
| CVE | Severity | Score | Published | Summary |
|---|---|---|---|---|
CVE-2018-19333 | Critical | 9.8 | 2018-11-17 | 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… |
CVE-2025-2713 | High | 7.8 | 2025-03-28 | Google gVisor's runsc component exhibited a local privilege escalation vulnerability due to incorrect handling of file access permissions, which allowed unpriv… |
CVE-2018-16359 | Medium | 6.8 | 2018-09-02 | 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. |
CVE-2018-20168 | Medium | 5.5 | 2018-12-17 | 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 ser… |
CVE-2024-10603 | Medium | 5.3 | 2025-01-30 | Weaknesses in the generation of TCP/UDP source ports and some other header values in Google's gVisor allowed them to be predicted by an external attacker in so… |
CVE-2024-10026 | Medium | 5.3 | 2025-01-30 | A weak hashing algorithm and small sizes of seeds/secrets in Google's gVisor allowed for a remote attacker to calculate a local IP address and a per-boot ident… |
CVE-2023-7258 | Medium | 4.8 | 2024-05-15 | A denial of service exists in Gvisor Sandbox where a bug in reference counting code in mount point tracking could lead to a panic, making it possible for an at… |