CVE-2017-9782

What it actually does

Heap-based buffer over-read in the jp2_decode function triggered by a specially crafted JP2 image, resulting in application crash.

Why it matters to the business

Attackers can crash applications that process untrusted images, causing service outages and potential loss of availability for image-handling workflows.

How an attack unfolds

An attacker supplies a malicious JP2 image to any process using the vulnerable JasPer library; the jp2_decode path performs an out-of-bounds read on the heap and terminates the process.

How to fix it

Upgrade the JasPer library to a version that resolves the over-read; for boring-registry-fips (Chainguard) install 0.13.2-r1 or later.

How to confirm the fix worked

Confirm the running binary or container image links against a fixed JasPer build; re-test with the original crafted image to verify the crash no longer occurs.

Typical attack path

1. Identify a target application that accepts user-supplied JP2/Jasper images
2. Craft a malformed JP2 file that triggers the buffer over-read in jp2_decode
3. Deliver the image via upload, email attachment, or network protocol
4. Trigger decoding, causing the process to crash

How to detect it

Review application crash logs and core dumps for signs of heap corruption during JP2 decoding; monitor for sudden restarts of image-processing services after receipt of new image files.

What your security team should do

• Apply the listed fixed version of boring-registry-fips immediately
• Inventory all other products that embed JasPer and schedule upgrades
• Add image-processing workloads to the vulnerability scanning pipeline
• Block or sanitize JP2 files at ingress points until patches are deployed