CVE-2023-43898

What it actually does

Null pointer dereference in stbi__convert_format during format conversion of malformed PIC images leads to immediate process crash.

Why it matters to the business

Applications that load images using the stb library become unavailable when users open attacker-supplied files, causing service interruptions and potential data loss in unsaved work.

How an attack unfolds

An attacker crafts a specially malformed PIC file that triggers the null dereference inside stbi__convert_format; the file is delivered to a victim who opens it with any application linked against the vulnerable stb image.h, resulting in an immediate denial-of-service crash.

How to fix it

Replace the stb image.h header with a version containing a bounds check before the format conversion call; rebuild and redeploy all dependent applications.

How to confirm the fix worked

Compile a test harness that calls stbi_load on the known crashing PIC sample and confirm the process no longer terminates; repeat after header replacement.

Typical attack path

1. Craft a PIC file that reaches stbi__convert_format with invalid internal pointers
2. Deliver the file via email, download, or removable media
3. Victim opens the file in an affected application
4. Library dereferences null pointer and crashes the process

How to detect it

Search application and system logs for segmentation faults or access violations that occur immediately after image-loading calls; correlate with file-open events involving .pic extensions.

• stbi__convert_format
• access violation.*stb_image
• signal 11.*pic

What your security team should do

• Inventory all products shipping stb image.h and schedule header replacement
• Add the library to the vulnerability scanning baseline
• Block or sandbox untrusted image files until patched builds are deployed