LiveActive security incident?Get immediate response
CVE Record

CVE-2016-10250: The jp2_colr_destroy function in jp2_cod.c in JasPer before 1.900.13 allows remote attackers to cause a den...

The jp2_colr_destroy function in jp2_cod.c in JasPer before 1.900.13 allows remote attackers to cause a denial of service (NULL pointer dereference) by leveraging incorrect cleanup of JP2 box data on error. NOTE: this vulnerability exists because of an incomplete fix for CVE-2016-8887.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

JasPer, a JPEG-2000 image library, had a crash bug before version 1.900.13. A malformed JP2 image could trigger a NULL pointer dereference during error cleanup, interrupting any service that processes untrusted JP2 files through the vulnerable library.

Executive priority

Treat this as a service-availability risk, not a confirmed data compromise issue. Prioritize remediation where public-facing or automated workflows parse untrusted images, especially if outages would affect customers or operations.

Technical view

CVE-2016-10250 affects jp2_colr_destroy in jp2_cod.c. Incorrect cleanup of JP2 box data on error can dereference NULL. The CVE notes this resulted from an incomplete fix for CVE-2016-8887. Sources identify JasPer before 1.900.13 and reference an upstream commit and Ubuntu advisory.

Likely exposure

Exposure is most likely in servers, desktop tools, or media pipelines that use JasPer before 1.900.13 to parse user-supplied JPEG-2000 or JP2 content. The source bundle does not identify specific downstream products beyond JasPer and vendor packages.

Exploitation context

The CVE states remote attackers can cause denial of service. There is no KEV listing and the provided sources do not establish active exploitation. Practical risk depends on whether crafted JP2 files can reach a vulnerable JasPer parser.

Researcher notes

The record has no CVSS or CWE data in the provided bundle. Analysis should stay limited to JasPer before 1.900.13 and vendor-patched packages. The key technical point is an incomplete CVE-2016-8887 fix causing unsafe cleanup on error.

Mitigation direction

  • Upgrade JasPer to 1.900.13 or a vendor-supported patched package.
  • Apply relevant distribution updates, including Ubuntu USN-3693-1 where applicable.
  • Reduce or disable untrusted JP2 processing where business workflows allow.
  • Run image parsing workloads with least privilege and process isolation.
  • Check vendor advisories for backported fixes in supported operating systems.

Validation and detection

  • Inventory systems and packages that include or link against JasPer.
  • Confirm installed JasPer versions or vendor package changelogs include this fix.
  • Review image upload, email, document, and media-processing paths for JP2 handling.
  • Check logs for crashes in services that process JPEG-2000 files.
  • Verify patched packages are deployed across build and runtime images.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2016-10250 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.