CVE-2014-9029: Multiple off-by-one errors in the (1) jpc_dec_cp_setfromcox and (2) jpc_dec_cp_setfromrgn functions in jpc/jpc_dec.c in JasPer 1.900.1 and…
Noroxi assessment
Priority: Monitor (action score 35/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 18.1% (FIRST EPSS); higher than 97.2% of all records.
- No special conditions are required; it is repeatable.
- Fixed version: jasper (Debian:6.0) 1.900.1-7+squeeze2; jasper (Debian:7) 1.900.1-13+deb7u1; jasper (openSUSE:Tumbleweed) 1.900.14-3.1.
Low priority for now. Upgrade to jasper (Debian:6.0) 1.900.1-7+squeeze2; jasper (Debian:7) 1.900.1-13+deb7u1; jasper (openSUSE:Tumbleweed) 1.900.14-3.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Multiple off-by-one errors in the (1) jpc_dec_cp_setfromcox and (2) jpc_dec_cp_setfromrgn functions in jpc/jpc_dec.c in JasPer 1.900.1 and earlier allow remote attackers to execute arbitrary code via a crafted jp2 file, which triggers a heap-based buffer overflow.
- Published
- Dec 8, 2014
- Updated
- Jun 16, 2026
- EPSS
- 18.1% · 97th percentile
- CWE
- CWE-189
Report tools
Action score
35
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 5 / 30 · 18.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| jasper project | jasper | cpe:2.3:a:jasper_project:jasper |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- jasper project jasperup to 1.900.1 inclusive
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:6.0 | jasper | before 1.900.1-7+squeeze2 | 1.900.1-7+squeeze2 |
| Debian:7 | jasper | before 1.900.1-13+deb7u1 | 1.900.1-13+deb7u1 |
| openSUSE:Tumbleweed | jasper | before 1.900.14-3.1 | 1.900.14-3.1 |
| Red Hat:enterprise_linux:6::client | jasper | before 0:1.900.1-16.el6_6.2 | 0:1.900.1-16.el6_6.2 |
| Red Hat:enterprise_linux:6::client | jasper-debuginfo | before 0:1.900.1-16.el6_6.2 | 0:1.900.1-16.el6_6.2 |
| Red Hat:enterprise_linux:6::client | jasper-devel | before 0:1.900.1-16.el6_6.2 | 0:1.900.1-16.el6_6.2 |
| Red Hat:enterprise_linux:6::client | jasper-libs | before 0:1.900.1-16.el6_6.2 | 0:1.900.1-16.el6_6.2 |
| Red Hat:enterprise_linux:6::client | jasper-utils | before 0:1.900.1-16.el6_6.2 | 0:1.900.1-16.el6_6.2 |
| Red Hat:enterprise_linux:7::client | jasper | before 0:1.900.1-26.el7_0.2 | 0:1.900.1-26.el7_0.2 |
| Red Hat:enterprise_linux:7::client | jasper-debuginfo | before 0:1.900.1-26.el7_0.2 | 0:1.900.1-26.el7_0.2 |
| Red Hat:enterprise_linux:7::client | jasper-devel | before 0:1.900.1-26.el7_0.2 | 0:1.900.1-26.el7_0.2 |
| Red Hat:enterprise_linux:7::client | jasper-libs | before 0:1.900.1-26.el7_0.2 | 0:1.900.1-26.el7_0.2 |
| Red Hat:enterprise_linux:7::client | jasper-utils | before 0:1.900.1-26.el7_0.2 | 0:1.900.1-26.el7_0.2 |
| Red Hat:rhev_manager:3 | rhevm-spice-client | before 0:3.5-3.el6 | 0:3.5-3.el6 |
| Red Hat:rhev_manager:3 | rhevm-spice-client-x64-cab | before 0:3.5-3.el6 | 0:3.5-3.el6 |
| Red Hat:rhev_manager:3 | rhevm-spice-client-x64-msi | before 0:3.5-3.el6 | 0:3.5-3.el6 |
| Red Hat:rhev_manager:3 | rhevm-spice-client-x86-cab | before 0:3.5-3.el6 | 0:3.5-3.el6 |
| Red Hat:rhev_manager:3 | rhevm-spice-client-x86-msi | before 0:3.5-3.el6 | 0:3.5-3.el6 |
Same product
jasper project: all recordsOther highest-scoring records for the same primary product.
- CVE-2008-3520Multiple integer overflows in JasPer 1.900.1 might allow context-dependent attackers to have an unknown impact via a crafted image file…38Monitor
- CVE-2015-8751Integer overflow in the jas_matrix_create function in JasPer allows context-dependent attackers to have unspecified impact via a crafted…36Monitor
- CVE-2018-19541An issue was discovered in JasPer 1.900.8, 1.900.9, 1.900.10, 1.900.11, 1.900.12, 1.900.13, 1.900.14, 1.900.15, 1.900.16, 1.900.17…36Monitor
Published before and after this one in the same product
- ← EarlierCVE-2011-4516Dec 14, 2011 · Heap-based buffer overflow in the jpc_cox_getcompparms function in libjasper/jpc/jpc_cs.c in JasPer 1.900.1 allows remote attackers to…30Monitor
- ← EarlierCVE-2011-4517Dec 14, 2011 · The jpc_crg_getparms function in libjasper/jpc/jpc_cs.c in JasPer 1.900.1 uses an incorrect data type during a certain size calculation…30Monitor
- Later →CVE-2014-8137Dec 24, 2014 · Double free vulnerability in the jas_iccattrval_destroy function in JasPer 1.900.1 and earlier allows remote attackers to cause a denial of…31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:jasper | 1.900.1-7+squeeze2 · Debian:6.0 | Package registry (OSV) |
| opensuse:jasper | 1.900.14-3.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:jasper | 0:1.900.1-16.el6_6.2 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:jasper-debuginfo | 0:1.900.1-16.el6_6.2 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:jasper-devel | 0:1.900.1-16.el6_6.2 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:jasper-libs | 0:1.900.1-16.el6_6.2 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:jasper-utils | 0:1.900.1-16.el6_6.2 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:rhevm-spice-client | 0:3.5-3.el6 · Red Hat:rhev_manager:3 | Package registry (OSV) |
| red hat:rhevm-spice-client-x64-cab | 0:3.5-3.el6 · Red Hat:rhev_manager:3 | Package registry (OSV) |
| red hat:rhevm-spice-client-x64-msi | 0:3.5-3.el6 · Red Hat:rhev_manager:3 | Package registry (OSV) |
| red hat:rhevm-spice-client-x86-cab | 0:3.5-3.el6 · Red Hat:rhev_manager:3 | Package registry (OSV) |
| red hat:rhevm-spice-client-x86-msi | 0:3.5-3.el6 · Red Hat:rhev_manager:3 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- P · data can be read
- Integrity
- P · data or configuration can be modified
- Availability
- P · the service can be disrupted
- Attack complexity
- Low
- Confidentiality impact
- P
- Integrity impact
- P
- Availability impact
- P
Weakness class (CWE)
CWE-189 · Numeric ErrorsCVSS vector
AV:N/AC:L/Au:N/C:P/I:P/A:P
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (17 more)Show less
- rhn.redhat.com/errata/RHSA-2014-2021.html
- rhn.redhat.com/errata/RHSA-2015-0698.html
- secunia.com/advisories/61747
- secunia.com/advisories/62828
- www.debian.org/security/2014/dsa-3089
- www.mandriva.com/security/advisories?name=MDVSA-2014:247
- www.mandriva.com/security/advisories?name=MDVSA-2015:159
- www.ocert.org/advisories/ocert-2014-009.html
- www.openwall.com/lists/oss-security/2014/12/04/9
- www.oracle.com/technetwork/security-advisory/cpujul2018-4258247.html
- www.securityfocus.com/archive/1/534153/100/0/threaded
- www.securityfocus.com/bid/71476
- www.slackware.com/security/viewer.php?l=slackware-security&y=2015&m=slackware-security.538606
- www.ubuntu.com/usn/USN-2434-1
- www.ubuntu.com/usn/USN-2434-2
- bugzilla.redhat.com/show_bug.cgi?id=1167537
- exchange.xforce.ibmcloud.com/vulnerabilities/99125
Vendor advisories and official records. Exploit/PoC links are deliberately left out.