| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.4 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in Jasper 1.900.17. Impacted is an unknown function of the file libjasper/jpc/jpc_dec.c. The manipulation leads to integer overflow. This vulnerability is documented as CVE-2017-5499. The attack can be initiated remotely. There is not any exploit available.
Details
A vulnerability was found in Jasper 1.900.17 (Programming Tool Software) and classified as problematic. This issue affects some unknown functionality of the file libjasper/jpc/jpc_dec.c. The manipulation with an unknown input leads to a integer overflow vulnerability. Using CWE to declare the problem leads to CWE-190. The product performs a calculation that can produce an integer overflow or wraparound, when the logic assumes that the resulting value will always be larger than the original value. This can introduce other weaknesses when the calculation is used for resource management or execution control. Impacted is availability. The summary by CVE is:
Integer overflow in libjasper/jpc/jpc_dec.c in JasPer 1.900.17 allows remote attackers to cause a denial of service (crash) via a crafted file.
The bug was discovered 03/01/2017. The weakness was released 03/01/2017 by Agostino Sarubbo with Gentoo (Website). The advisory is shared at securityfocus.com. The identification of this vulnerability is CVE-2017-5499 since 01/16/2017. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available.
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 95666†). Entries connected to this vulnerability are available at VDB-97420, VDB-97422, VDB-97423 and VDB-97424. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.4VulDB Meta Temp Score: 5.4
VulDB Base Score: 5.3
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.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: Integer overflowCWE: CWE-190 / CWE-189
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
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
01/16/2017 🔍01/16/2017 🔍
03/01/2017 🔍
03/01/2017 🔍
03/01/2017 🔍
03/02/2017 🔍
09/03/2020 🔍
Sources
Advisory: securityfocus.com⛔Researcher: Agostino Sarubbo
Organization: Gentoo
Status: Not defined
CVE: CVE-2017-5499 (🔍)
GCVE (CVE): GCVE-0-2017-5499
GCVE (VulDB): GCVE-100-97421
SecurityFocus: 95666 - JasPer Multiple Denial of Service Vulnerabilities
OSVDB: - CVE-2017-5499 - JasPer - Integer Overflow Issue
See also: 🔍
Entry
Created: 03/02/2017 10:00Updated: 09/03/2020 10:38
Changes: 03/02/2017 10:00 (58), 09/03/2020 10:38 (6)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.