Jasper 2.0.13 jpc/jpc_dec.c jpc_dec_tileinit resource consumption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.4 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Jasper 2.0.13. It has been rated as problematic. This affects the function jpc_dec_tileinit of the file jpc/jpc_dec.c. Performing a manipulation results in resource consumption.
This vulnerability was named CVE-2017-14229. The attack may be initiated remotely. There is no available exploit.
Details
A vulnerability was found in Jasper 2.0.13 (Programming Tool Software). It has been classified as problematic. This affects the function jpc_dec_tileinit of the file jpc/jpc_dec.c. The manipulation with an unknown input leads to a resource consumption vulnerability. CWE is classifying the issue as CWE-400. The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources. This is going to have an impact on availability. The summary by CVE is:
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.
The bug was discovered 09/09/2017. The weakness was presented 09/09/2017 (Website). It is possible to read the advisory at securityfocus.com. This vulnerability is uniquely identified as CVE-2017-14229 since 09/09/2017. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1499 according to MITRE ATT&CK.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at SecurityFocus (BID 100861†). See VDB-95087, VDB-105939, VDB-117405 and VDB-125265 for similar entries. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.4
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Resource consumptionCWE: CWE-400 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
09/09/2017 🔍09/09/2017 🔍
09/09/2017 🔍
09/09/2017 🔍
09/10/2017 🔍
09/11/2017 🔍
12/28/2022 🔍
Sources
Advisory: 146⛔Researcher: team OWL337
Status: Not defined
Confirmation: 🔍
CVE: CVE-2017-14229 (🔍)
GCVE (CVE): GCVE-0-2017-14229
GCVE (VulDB): GCVE-100-106323
SecurityFocus: 100861 - JasPer 'jpc_dec.c' Denial of Service Vulnerability
See also: 🔍
Entry
Created: 09/10/2017 19:05Updated: 12/28/2022 09:42
Changes: 09/10/2017 19:05 (53), 11/14/2019 11:58 (10), 01/11/2021 14:24 (3), 12/28/2022 09:42 (2)
Complete: 🔍
Cache ID: 216:269:103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.