8.2 CVE-2025-22225
CISA Kev Catalog
VMware ESXi contains an arbitrary write vulnerability. A malicious actor with privileges within the VMX process may trigger an arbitrary kernel write leading to an escape of the sandbox.
https://nvd.nist.gov/vuln/detail/CVE-2025-22225
Categories
CWE-787 : Out-of-bounds Write
The product writes data past the end, or before the beginning, of the intended buffer. At the point when the product writes data to an invalid location, it is likely that a separate weakness already occurred earlier. For example, the product might alter an index, perform incorrect pointer arithmetic, initialize or release memory incorrectly, etc., thus referencing a memory location outside the buffer. Often used to describe the consequences of writing to memory outside the bounds of a buffer, or to memory that is otherwise invalid. This weakness can be detected using dynamic tools and techniques that interact with the software using large test suites with many diverse inputs, such as fuzz testing (fuzzing), robustness testing, and fault injection. The software's operation may slow down, but it should not become unstable, crash, or generate incorrect results. Replace unbounded copy functions with analogous functions that support length arguments, such as strcpy with strncpy. Create these if they are not available. The reference implementation code for a Trusted Platform Module does not implement length checks on data, allowing for an attacker to write 2 bytes past the end of a buffer. Chain: insufficient input validation (CWE-20) in browser allows heap corruption (CWE-787), as exploited in the wild per CISA KEV. GPU kernel driver allows memory corruption because a user can obtain read/write access to read-only pages, as exploited in the wild per CISA KEV. Chain: integer truncation (CWE-197) causes small buffer allocation (CWE-131) leading to out-of-bounds write (CWE-787) in kernel pool, as exploited in the wild per CISA KEV. Out-of-bounds write in kernel-mode driver, as exploited in the wild per CISA KEV. Escape from browser sandbox using out-of-bounds write due to incorrect bounds check, as exploited in the wild per CISA KEV. Memory corruption in web browser scripting engine, as exploited in the wild per CISA KEV. chain: mobile phone Bluetooth implementation does not include offset when calculating packet length (CWE-682), leading to out-of-bounds write (CWE-787) Chain: compiler optimization (CWE-733) removes or modifies code used to detect integer overflow (CWE-190), allowing out-of-bounds write (CWE-787). malformed inputs cause accesses of uninitialized or previously-deleted objects, leading to memory corruption chain: -1 value from a function call was intended to indicate an error, but is used as an array index instead. Unchecked length of SSLv2 challenge value leads to buffer underflow. Buffer underflow from a small size value with a large buffer (length parameter inconsistency, CWE-130) Chain: integer signedness error (CWE-195) passes signed comparison, leading to heap overflow (CWE-122) Classic stack-based buffer overflow in media player using a long entry in a playlist Heap-based buffer overflow in media player using a long entry in a playlist
CWE-123 : Write-what-where Condition
Any condition where the attacker has the ability to write an arbitrary value to an arbitrary location, often as the result of a buffer overflow. Use a language that provides appropriate memory abstractions. Use OS-level preventative functionality integrated after the fact. Not a complete solution. Chain: Python library does not limit the resources used to process images that specify a very large number of bands (CWE-1284), leading to excessive memory consumption (CWE-789) or an integer overflow (CWE-190). Chain: 3D renderer has an integer overflow (CWE-190) leading to write-what-where condition (CWE-123) using a crafted image.
References
CPE
| cpe | start | end |
|---|---|---|
| Configuration 1 | ||
| cpe:2.3:o:vmware:esxi:7.0:-:*:*:*:*:*:* | ||
| cpe:2.3:o:vmware:esxi:7.0:beta:*:*:*:*:*:* | ||
| cpe:2.3:o:vmware:esxi:7.0:update_1:*:*:*:*:*:* | ||
| cpe:2.3:o:vmware:esxi:7.0:update_1a:*:*:*:*:*:* | ||
| cpe:2.3:o:vmware:esxi:7.0:update_1b:*:*:*:*:*:* | ||
| cpe:2.3:o:vmware:esxi:7.0:update_1c:*:*:*:*:*:* | ||
| cpe:2.3:o:vmware:esxi:7.0:update_1d:*:*:*:*:*:* | ||
| cpe:2.3:o:vmware:esxi:7.0:update_1e:*:*:*:*:*:* | ||
| cpe:2.3:o:vmware:esxi:7.0:update_2:*:*:*:*:*:* | ||
| cpe:2.3:o:vmware:esxi:7.0:update_2a:*:*:*:*:*:* | ||
| cpe:2.3:o:vmware:esxi:7.0:update_2c:*:*:*:*:*:* | ||
| cpe:2.3:o:vmware:esxi:7.0:update_2d:*:*:*:*:*:* | ||
| cpe:2.3:o:vmware:esxi:7.0:update_2e:*:*:*:*:*:* | ||
| cpe:2.3:o:vmware:esxi:7.0:update_3:*:*:*:*:*:* | ||
| cpe:2.3:o:vmware:esxi:7.0:update_3c:*:*:*:*:*:* | ||
| cpe:2.3:o:vmware:esxi:7.0:update_3d:*:*:*:*:*:* | ||
| cpe:2.3:o:vmware:esxi:7.0:update_3e:*:*:*:*:*:* | ||
| cpe:2.3:o:vmware:esxi:7.0:update_3f:*:*:*:*:*:* | ||
| cpe:2.3:o:vmware:esxi:7.0:update_3g:*:*:*:*:*:* | ||
| cpe:2.3:o:vmware:esxi:7.0:update_3i:*:*:*:*:*:* | ||
| cpe:2.3:o:vmware:esxi:7.0:update_3j:*:*:*:*:*:* | ||
| cpe:2.3:o:vmware:esxi:7.0:update_3k:*:*:*:*:*:* | ||
| cpe:2.3:o:vmware:esxi:7.0:update_3l:*:*:*:*:*:* | ||
| cpe:2.3:o:vmware:esxi:7.0:update_3m:*:*:*:*:*:* | ||
| cpe:2.3:o:vmware:esxi:7.0:update_3n:*:*:*:*:*:* | ||
| cpe:2.3:o:vmware:esxi:7.0:update_3o:*:*:*:*:*:* | ||
| cpe:2.3:o:vmware:esxi:7.0:update_3p:*:*:*:*:*:* | ||
| cpe:2.3:o:vmware:esxi:7.0:update_3q:*:*:*:*:*:* | ||
| cpe:2.3:o:vmware:esxi:7.0:update_3r:*:*:*:*:*:* | ||
| cpe:2.3:o:vmware:esxi:8.0:-:*:*:*:*:*:* | ||
| cpe:2.3:o:vmware:esxi:8.0:a:*:*:*:*:*:* | ||
| cpe:2.3:o:vmware:esxi:8.0:b:*:*:*:*:*:* | ||
| cpe:2.3:o:vmware:esxi:8.0:c:*:*:*:*:*:* | ||
| cpe:2.3:o:vmware:esxi:8.0:update_1:*:*:*:*:*:* | ||
| cpe:2.3:o:vmware:esxi:8.0:update_1a:*:*:*:*:*:* | ||
| cpe:2.3:o:vmware:esxi:8.0:update_1c:*:*:*:*:*:* | ||
| cpe:2.3:o:vmware:esxi:8.0:update_1d:*:*:*:*:*:* | ||
| cpe:2.3:o:vmware:esxi:8.0:update_2:*:*:*:*:*:* | ||
| cpe:2.3:o:vmware:esxi:8.0:update_2b:*:*:*:*:*:* | ||
| cpe:2.3:o:vmware:esxi:8.0:update_2c:*:*:*:*:*:* | ||
| cpe:2.3:o:vmware:esxi:8.0:update_3:*:*:*:*:*:* | ||
| cpe:2.3:o:vmware:esxi:8.0:update_3b:*:*:*:*:*:* | ||
| cpe:2.3:o:vmware:esxi:8.0:update_3c:*:*:*:*:*:* | ||
| Configuration 2 | ||
| cpe:2.3:a:vmware:cloud_foundation:-:*:*:*:*:*:*:* | ||
| cpe:2.3:a:vmware:telco_cloud_infrastructure:2.2:*:*:*:*:*:*:* | ||
| cpe:2.3:a:vmware:telco_cloud_infrastructure:2.5:*:*:*:*:*:*:* | ||
| cpe:2.3:a:vmware:telco_cloud_infrastructure:2.7:*:*:*:*:*:*:* | ||
| cpe:2.3:a:vmware:telco_cloud_infrastructure:3.0:*:*:*:*:*:*:* | ||
| cpe:2.3:a:vmware:telco_cloud_platform:2.0:*:*:*:*:*:*:* | ||
| cpe:2.3:a:vmware:telco_cloud_platform:2.5:*:*:*:*:*:*:* | ||
| cpe:2.3:a:vmware:telco_cloud_platform:2.7:*:*:*:*:*:*:* | ||
| cpe:2.3:a:vmware:telco_cloud_platform:3.0:*:*:*:*:*:*:* | ||
| cpe:2.3:a:vmware:telco_cloud_platform:4.0:*:*:*:*:*:*:* | ||
| cpe:2.3:a:vmware:telco_cloud_platform:4.0.1:*:*:*:*:*:*:* | ||
| cpe:2.3:a:vmware:telco_cloud_platform:5.0:*:*:*:*:*:*:* | ||
REMEDIATION
EXPLOITS
Exploit-db.com
| id | description | date | |
|---|---|---|---|
| No known exploits | |||
POC Github
| Url |
|---|
| No known exploits |
Other Nist (github, ...)
| Url |
|---|
| No known exploits |
CAPEC
Common Attack Pattern Enumerations and Classifications
| id | description | severity |
|---|---|---|
| No entry | ||
Cybersecurity needs ?
Strengthen software security from the outset with our DevSecOps expertise
Integrate security right from the start of the software development cycle for more robust applications and greater customer confidence.
Our team of DevSecOps experts can help you secure your APIs, data pipelines, CI/CD chains, Docker containers and Kubernetes deployments.
