Stack-based buffer overflow in OpenJPEG before 1.5.2 allows remote attackers to have unspecified impact via unknown vectors to (1) lib/open…

published 2014-04-18 12y ago modified 2026-06-16 4mo ago also EUVD-2013-4186

cvss: 10.0; version 2.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 3.0%; EPSS 3.0% chance of exploitation in 30 days, percentile 87%
public exploits: 0; none known

Stack-based buffer overflow in OpenJPEG before 1.5.2 allows remote attackers to have unspecified impact via unknown vectors to (1) lib/openjp3d/opj_jp3d_compress.c, (2) bin/jp3d/convert.c, or (3) lib/openjp3d/event.c.

Is CVE-2013-4290 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2013-4290 updated 2026-11-04 cvss 6.8

openjpeg: multiple stack-based buffer overflows

Red Hat Enterprise Linux 6 openjpeg, openjpeg-libs Red Hat Enterprise Linux 7 openjpeg, openjpeg-libs
not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

2.99% chance of exploitation in the next 30 days, higher than 87% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

seclists.org http://seclists.org/oss-sec/2013/q3/593 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
NVD	2.0	10.0	AV:N/AC:L/Au:N/C:C/I:C/A:C

Classification

Weakness

CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

References

seclists.org /oss-sec/2013/q3/593
mailing-list, exploit
secunia.com /advisories/57285
third-party-advisory, vendor-advisory
openjpeg.googlecode.com /svn/tags/version.1.5.2/NEWS
securityfocus.com /bid/62362
vdb-entry

Sources

CVE List CVE-2013-4290
NVD CVE-2013-4290

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.