CVE-2024-28577

What it actually does

Null pointer dereference in jpeg_read_exif_profile_raw() causes immediate process crash when parsing specially crafted JPEG files.

Why it matters to the business

Applications that process user-supplied JPEG images become unavailable until restarted, disrupting workflows that rely on image handling libraries.

How an attack unfolds

An attacker supplies a JPEG image containing malformed EXIF data to any application linked against the vulnerable FreeImage library; the library dereferences a null pointer inside jpeg_read_exif_profile_raw and terminates.

How to fix it

Upgrade FreeImage to a version containing the fix for the null dereference; rebuild and redeploy all dependent applications. Where immediate patching is impossible, add input validation or sandboxing around JPEG processing.

How to confirm the fix worked

Confirm the installed FreeImage binary no longer contains the vulnerable jpeg_read_exif_profile_raw implementation and that crafted test images no longer cause crashes.

Typical attack path

1. Identify an application that accepts JPEG input and uses FreeImage 3.19.0
2. Craft a JPEG file that triggers the null dereference in jpeg_read_exif_profile_raw
3. Deliver the file through normal application channels (upload, open, preview)
4. Observe application crash and denial of service

How to detect it

Review application and system logs for abrupt terminations or segmentation faults that coincide with JPEG processing activity; correlate with file-upload or image-open events.

What your security team should do

• Prioritize patching of any internet-facing or multi-tenant services that accept JPEG images
• Scan build pipelines and package repositories for the vulnerable FreeImage version
• Implement runtime monitoring for unexpected process terminations during image handling