Gvisor

gvisor

Vendor: Google • 7 CVEs

CVEs (7)

CVE VENDORS PRODUCTS UPDATED PUBLISHED CVSS
CVE-2025-2713 1Google 1Gvisor Jun 17, 2026 Mar 28, 2025 6.8 MEDIUM· v4 7.8 HIGH· v3 N/A· v2 Google gVisor's runsc component exhibited a local privilege escalation vulnerability due to incorrect handling of file access permissions, which allowed unprivileged users to access restricted files. This occurred becaus...Show more Google gVisor's runsc component exhibited a local privilege escalation vulnerability due to incorrect handling of file access permissions, which allowed unprivileged users to access restricted files. This occurred because the process initially ran with root-like permissions until the first fork.Show less
CVE-2024-10603 1Google 1Gvisor Jun 17, 2026 Jan 30, 2025 6.3 MEDIUM· v4 5.3 MEDIUM· v3 N/A· v2 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 some circumstances.
CVE-2024-10026 1Google 1Gvisor Jun 17, 2026 Jan 30, 2025 6.3 MEDIUM· v4 5.3 MEDIUM· v3 N/A· v2 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 identifier that could aid in tracking of a device in certain circu...Show more 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 identifier that could aid in tracking of a device in certain circumstances.Show less
CVE-2023-7258 1Google 1Gvisor Jun 17, 2026 May 15, 2024 N/A· v4 6.5 MEDIUM· v3 N/A· v2 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 attacker running as root and with permission to mount volumes t...Show more 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 attacker running as root and with permission to mount volumes to kill the sandbox. We recommend upgrading past commit 6a112c60a257dadac59962e0bc9e9b5aee70b5b6Show less
CVE-2018-20168 1Google 1Gvisor Nov 21, 2024 Dec 17, 2018 N/A· v4 5.5 MEDIUM· v3 4.3 MEDIUM· v2 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 appli...Show more 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.Show less
CVE-2018-19333 1Google 1Gvisor Nov 21, 2024 Nov 17, 2018 N/A· v4 9.8 CRITICAL· v3 7.5 HIGH· v2 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, becaus...Show more 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.Show less
CVE-2018-16359 1Google 1Gvisor Nov 21, 2024 Sep 2, 2018 N/A· v4 6.8 MEDIUM· v3 7.1 HIGH· v2 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.