Jasper 2.0.12 jpc/jpc_t1cod.c JPC_NOMINALGAIN input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.3 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in Jasper 2.0.12. The affected element is the function JPC_NOMINALGAIN of the file jpc/jpc_t1cod.c. The manipulation leads to input validation.
This vulnerability is uniquely identified as CVE-2017-13753. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability was found in Jasper 2.0.12 (Programming Tool Software). It has been rated as problematic. This issue affects the function JPC_NOMINALGAIN of the file jpc/jpc_t1cod.c. The manipulation with an unknown input leads to a input validation vulnerability. Using CWE to declare the problem leads to CWE-20. The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly. Impacted is availability. The summary by CVE is:
There is a reachable assertion abort in the function JPC_NOMINALGAIN() in jpc/jpc_t1cod.c in JasPer 2.0.12 that will lead to a remote denial of service attack.
The bug was discovered 08/29/2017. The weakness was disclosed 08/29/2017 (Website). It is possible to read the advisory at bugzilla.redhat.com. The identification of this vulnerability is CVE-2017-13753 since 08/29/2017. The attack may be initiated remotely. Technical details of the vulnerability are known, but there is no available exploit.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entries VDB-105946, VDB-105945, VDB-105944 and VDB-105943 are pretty similar. 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: 4.3VulDB Meta Temp Score: 4.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: Input validationCWE: CWE-20
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
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
08/29/2017 🔍08/29/2017 🔍
08/29/2017 🔍
08/30/2017 🔍
01/10/2021 🔍
Sources
Advisory: bugzilla.redhat.comStatus: Not defined
CVE: CVE-2017-13753 (🔍)
GCVE (CVE): GCVE-0-2017-13753
GCVE (VulDB): GCVE-100-105947
See also: 🔍
Entry
Created: 08/30/2017 08:58Updated: 01/10/2021 11:49
Changes: 08/30/2017 08:58 (39), 11/11/2019 19:59 (3), 01/10/2021 11:49 (8)
Complete: 🔍
Cache ID: 216::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.