CVE-2023-49462
High · 8.8CVSS
8.8
EPSS
0.8%
Published
Dec 7, 2023
CISA due date
—
Cloudanix analysis
A problem in an image processing library can let attackers take control of systems or crash services simply by making the software open a specially crafted image file.
- Exploitation
- Requires User Interaction
- Attacker needs
- User Interaction
- Complexity
- Moderate
- Impact
- Denial Of Service
- Component
- Library
- Class
- Memory Corruption
- Remediation
- Upgrade
- Effort
- Medium
- Patch risk
- Low
What it actually does
A segmentation violation in the EXIF parsing component of libheif (/libheif/exif.cc) triggers memory corruption that can be leveraged for arbitrary code execution or denial of service when processing crafted HEIF images.
Why it matters to the business
Media-processing applications, viewers, and downstream software that rely on this library face service outages, potential full system compromise, and data exposure risks; the multi-year age of the issue combined with available exploits and broad ecosystem use heightens operational and compliance exposure.
How an attack unfolds
An attacker supplies a malicious HEIF file containing malformed EXIF metadata that triggers the segmentation fault during parsing; the resulting memory corruption allows control-flow hijacking to achieve code execution on the victim system.
How to fix it
Upgrade libheif to the latest available release that resolves the EXIF handling flaw; until a fixed version is deployed, disable EXIF metadata processing or isolate image handling in sandboxed processes.
How to confirm the fix worked
Verify the deployed libheif version against vendor releases; test with known trigger images to confirm absence of crashes or unexpected memory behavior; review application dependency manifests for the vulnerable component.
Typical attack path
- Craft and host a malicious HEIF image containing malformed EXIF data
- Deliver the image through web, email, file upload, or shared storage
- Victim application loads the image and invokes libheif EXIF parsing
- Segmentation violation occurs, enabling memory corruption exploitation
How to detect it
Review application and system logs for segmentation faults or abrupt terminations during HEIF image processing; correlate crashes with inbound or processed image files of suspicious origin.
What your security team should do
- Immediately inventory all systems and applications using libheif and schedule upgrades
- Apply compensating controls such as input sanitization and sandboxing for image processing
- Monitor upstream libheif releases for the official fix and deploy promptly
The record
libheif v1.17.5 was discovered to contain a segmentation violation via the component /libheif/exif.cc.
Affected packages
| Ecosystem | Package | Introduced | Fixed |
|---|---|---|---|
| Debian:11 | libheif | 0 | No fix |
| Debian:12 | libheif | 0 | No fix |
| Debian:12 | libheif | 0 | 1.15.1-1+deb12u1 |
| Debian:13 | libheif | 0 | 1.17.6-1 |
| Mageia:9 | libheif | 0 | 1.16.2-1.1.mga9 |
| Mageia:9 | libheif | 0 | 1.16.2-1.1.mga9.tainted |
| Ubuntu:23.10 | libheif | 0 | 1.16.2-2ubuntu1.1 |
| Ubuntu:24.04:LTS | libheif | 0 | 1.17.6-1ubuntu4 |
| Ubuntu:Pro:18.04:LTS | libheif | 0 | 1.1.0-2ubuntu0.1~esm1 |
| Ubuntu:Pro:20.04:LTS | libheif | 0 | 1.6.1-1ubuntu0.1~esm1 |
| Ubuntu:Pro:22.04:LTS | libheif | 0 | 1.12.0-2ubuntu0.1~esm1 |
Related vulnerabilities
- CVE-2024-41311 In Libheif 1.17.6, insufficient checks in ImageOverlay::parse() decoding a heif file… Also affects libheif
- CVE-2024-25269 libheif <= 1.17.6 contains a memory leak in the function JpegEncoder::Encode. Also affects libheif
- CVE-2023-49463 libheif v1.17.5 was discovered to contain a segmentation violation via the function… Also affects libheif
- CVE-2023-49460 libheif v1.17.5 was discovered to contain a segmentation violation via the function… Also affects libheif
- CVE-2023-49464 libheif v1.17.5 was discovered to contain a segmentation violation via the function… Also affects libheif