CVE-2017-17912

What it actually does

Heap-based buffer over-read in ReadNewsProfile when processing TIFF images, where LocaleNCompare accesses memory past the allocated region.

Why it matters to the business

Processing untrusted images can leak sensitive memory contents or cause crashes, disrupting image-handling services and risking data exposure in graphics workflows.

How an attack unfolds

An attacker supplies a specially crafted TIFF file that triggers the over-read during NewsProfile parsing; the flaw allows reading heap data beyond bounds, potentially disclosing memory or leading to denial of service.

How to fix it

Upgrade GraphicsMagick to a version after the 2017-12-17 snapshot that resolves the over-read in coders/tiff.c; apply distribution updates for Debian and rebuild any dependent packages.

How to confirm the fix worked

Reprocess known triggering TIFF samples under memory sanitizers or bounds-checking builds and confirm no over-read occurs; verify updated package versions are installed.

Typical attack path

1. Craft malicious TIFF image exploiting the NewsProfile buffer over-read
2. Deliver image to application using vulnerable GraphicsMagick for processing
3. Trigger ReadNewsProfile via image load or conversion
4. Read or crash on out-of-bounds heap memory

How to detect it

Review application logs for abnormal TIFF processing errors or crashes involving coders/tiff.c; inspect heap dumps or sanitizer reports from image-handling services for over-read patterns.

What your security team should do

• Immediately update GraphicsMagick packages across all environments
• Restrict image processing to sanitized or trusted inputs
• Monitor for new GraphicsMagick releases and apply patches promptly
• Consider sandboxing or replacing the library in high-risk pipelines