CVE-2017-14229 json
There is an infinite loop in the jpc_dec_tileinit function in jpc/jpc_dec.c of Jasper 2.0.13.
published 2017-09-09 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-5739
- cvss
- 7.5
- version 3.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
Summary
There is an infinite loop in the jpc_dec_tileinit function in jpc/jpc_dec.c of Jasper 2.0.13. It will lead to a remote denial of service attack.
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-2017-14229 updated cvss 3.3
jasper: excessive looping in jpc_dec_tileinit()
-
Red Hat Enterprise Linux 5 netpbm Red Hat Enterprise Linux 6 jasper, jasper-libs, jasper-utils Red Hat Enterprise Linux 7 jasper, jasper-libs, jasper-utils Red Hat Enterprise Virtualization 3 mingw-virt-viewer, mingw32-virt-viewer, mingw64-virt-viewernot 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
3.00% chance of exploitation in the next 30 days, higher than 87% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:N/A:P |
Classification
- Weakness
-
- CWE-835 Loop with Unreachable Exit Condition
References
-
security.gentoo.org
/glsa/201908-03
vendor-advisory
- oracle.com /technetwork/security-advisory/cpujan2019-5072801.html
-
securityfocus.com
/bid/100861
vdb-entry
-
github.com
/mdadams/jasper/issues/146
third-party-advisory
Sources
- CVE List CVE-2017-14229
- NVD CVE-2017-14229
Fencer Vulns 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.