Out-of-Bounds Read in Microsoft HEIF Image Extensions Facilitates Potential Memory Corruption
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | n/a | affected |
|
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Microsoft | Heif Image Extension |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: 1.1% (1.052% probability within 30 days)
| Link | Providers |
|---|---|
| https://github.com/hyunjungg/CVE-2025-62821 |
|
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-125 | |
| Metrics |
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Microsoft
Microsoft heif Image Extension |
|
| Vendors & Products |
Microsoft
Microsoft heif Image Extension |
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Out-of-Bounds Read in Microsoft HEIF Image Extensions Facilitates Potential Memory Corruption | |
| Weaknesses | CWE-20 |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Microsoft HEIF Image Extensions 1.2.22.0 has an out-of-bounds read because CHEIFItemInfoEntry_GetDataSize can return success while leaving the reported data size as 0. This causes a caller to make a 1-byte allocation. Later, CopyPixels computes copy_size = stride * abs(roi_height) but does not check the source buffer length before a memmove call. | |
| References |
|