Skip to main content
Mallory
MediumVulnerability

CVE-2016-10504: Heap-based Buffer Overflow in OpenJPEG opj_mqc_byteout

Published Aug 30, 2017 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS6.5Medium · v3
EPSS8.2%95th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Uclouvain
IdentifiersCVE-2016-10504CWE-122

A heap-based buffer overflow exists in the opj_mqc_byteout function in mqc.c in OpenJPEG versions prior to 2.2.0. This vulnerability can be triggered by a specially crafted BMP file, which causes the application to write outside the bounds of a heap-allocated buffer, leading to memory corruption and a potential application crash.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Exploitation of this vulnerability allows remote attackers to cause a denial of service (application crash) by sending a crafted BMP file to an application using a vulnerable version of OpenJPEG. While the primary impact is denial of service, memory corruption could potentially be leveraged for further exploitation, though no such exploitation has been demonstrated.

Mitigation

If you can’t patch tonight, do this now.

If immediate upgrade is not possible, restrict processing of untrusted BMP files and consider running applications using OpenJPEG in a sandboxed environment to limit the impact of potential exploitation.

Remediation

Patch, then assume compromise.

Upgrade OpenJPEG to version 2.2.0 or later, where the vulnerable code in opj_mqc_byteout has been patched to prevent the buffer overflow condition.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
Candidate exploits are awaiting analysis. View them in Mallory.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
UclouvainOpenjpegapplication
FAQ

Frequently asked questions

Is CVE-2016-10504 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2016-10504 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2016-10504?
As of Oct 16, 2026, Mallory has not confirmed a public exploit for CVE-2016-10504. 1 candidate exploit record is not yet analyzed.
Is there a patch for CVE-2016-10504?
Upgrade OpenJPEG to version 2.2.0 or later, where the vulnerable code in opj_mqc_byteout has been patched to prevent the buffer overflow condition.
What products are affected by CVE-2016-10504?
Uclouvain Openjpeg.
How severe is CVE-2016-10504?
CVE-2016-10504 has a CVSS v3 score of 6.5 (Medium) and an EPSS score of 8.2% (95th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

No public activity tracked yet. Mallory keeps watching.

View more in app →

No public activity observed for this vulnerability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.