CVE-2024-28575

What it actually does

Buffer overflow in the opj_j2k_read_mct function during J2K image parsing leads to denial of service via application crash.

Why it matters to the business

Applications processing image files can experience unexpected crashes and service interruptions when handling certain inputs, increasing operational downtime.

How an attack unfolds

A local attacker crafts a malicious J2K image file and supplies it to an application using the vulnerable library, triggering the overflow in opj_j2k_read_mct to cause a crash without requiring elevated privileges.

How to fix it

Upgrade affected components to the fixed versions provided, such as python3-dasbus to 1.2-2.el8 on AlmaLinux 8, and rebuild or redeploy dependent applications.

How to confirm the fix worked

Confirm the installed library version matches or exceeds the fixed release and test image processing functionality with both valid and edge-case J2K files to ensure stability.

Typical attack path

1. Locate an application that depends on the vulnerable image processing library
2. Prepare a specially crafted J2K format image file
3. Induce the target application to load and parse the malicious image
4. Trigger the buffer overflow resulting in denial of service

How to detect it

Review application and system logs for crashes or segmentation faults occurring during J2K image processing and correlate with file access events.

What your security team should do

• Prioritize updating to the specified fixed versions across all affected systems
• Inventory applications that parse J2K images and schedule patching
• Implement input validation or sandboxing for image processing where updates are delayed