struktur libheif up to 1.19.5 image-items/grid.cc get_decoder null pointer dereference
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 2.6 | $0-$5k | 0.00 |
Summary
A vulnerability marked as problematic has been reported in struktur libheif up to 1.19.5. Affected by this issue is the function ImageItem_Grid::get_decoder of the file image-items/grid.cc. Performing a manipulation results in null pointer dereference.
This vulnerability is reported as CVE-2025-43967. The attack requires a local approach. No exploit exists.
It is suggested to upgrade the affected component.
Details
A vulnerability classified as problematic has been found in struktur libheif up to 1.19.5. This affects the function ImageItem_Grid::get_decoder of the file image-items/grid.cc. The manipulation with an unknown input leads to a null pointer dereference vulnerability. CWE is classifying the issue as CWE-476. A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit. This is going to have an impact on availability. The summary by CVE is:
libheif before 1.19.6 has a NULL pointer dereference in ImageItem_Grid::get_decoder in image-items/grid.cc because a grid image can reference a nonexistent image item.
The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2025-43967 since 04/20/2025. The exploitability is told to be difficult. An attack has to be approached locally. Technical details are known, but no exploit is available.
The vulnerability scanner Nessus provides a plugin with the ID 253450 (TencentOS Server 4: libheif (TSSA-2025:0631)), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 1.19.6 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying the patch 6e35af7b0ff9fb6cc952a1539590d160db32f671 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the databases at Tenable (253450) and EUVD (EUVD-2025-11957). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 2.7VulDB Meta Temp Score: 2.6
VulDB Base Score: 2.5
VulDB Temp Score: 2.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 2.9
CNA Vector (MITRE): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Null pointer dereferenceCWE: CWE-476 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 253450
Nessus Name: TencentOS Server 4: libheif (TSSA-2025:0631)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: libheif 1.19.6
Patch: 6e35af7b0ff9fb6cc952a1539590d160db32f671
Timeline
04/20/2025 🔍04/21/2025 🔍
04/21/2025 🔍
08/21/2025 🔍
Sources
Advisory: 1455Status: Confirmed
CVE: CVE-2025-43967 (🔍)
GCVE (CVE): GCVE-0-2025-43967
GCVE (VulDB): GCVE-100-305757
EUVD: 🔍
Entry
Created: 04/21/2025 03:05Updated: 08/21/2025 21:40
Changes: 04/21/2025 03:05 (69), 05/24/2025 23:26 (1), 08/21/2025 21:40 (2)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.