Jasper 2.0.14 libjasper/jpc/jpc_enc.c jpc_abstorelstepsize input validation
| 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 2.0.14. Affected by this issue is the function jpc_abstorelstepsize of the file libjasper/jpc/jpc_enc.c. Performing a manipulation results in input validation.
This vulnerability is reported as CVE-2018-9252. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability classified as problematic has been found in Jasper 2.0.14 (Programming Tool Software). This affects the function jpc_abstorelstepsize of the file libjasper/jpc/jpc_enc.c. The manipulation with an unknown input leads to a input validation vulnerability. CWE is classifying the issue as 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. This is going to have an impact on availability. The summary by CVE is:
JasPer 2.0.14 allows denial of service via a reachable assertion in the function jpc_abstorelstepsize in libjasper/jpc/jpc_enc.c.
The bug was discovered 04/03/2018. The weakness was disclosed 04/04/2018 (Website). The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2018-9252 since 04/03/2018. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. It demands that the victim is doing some kind of user interaction. 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.
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: 4.3
VulDB Temp Score: 4.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.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: Input validationCWE: CWE-20
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
04/03/2018 🔍04/03/2018 🔍
04/03/2018 🔍
04/04/2018 🔍
04/04/2018 🔍
02/26/2023 🔍
Sources
Advisory: 173Status: Not defined
CVE: CVE-2018-9252 (🔍)
GCVE (CVE): GCVE-0-2018-9252
GCVE (VulDB): GCVE-100-115677
Entry
Created: 04/04/2018 12:47Updated: 02/26/2023 15:06
Changes: 04/04/2018 12:47 (56), 01/21/2020 10:24 (1), 02/26/2023 15:06 (3)
Complete: 🔍
Cache ID: 216:2FA: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.