OpenJPEG up to 2.3.0 openmj2/pi.c pi_next_pcrl/pi_next_cprl/pi_next_rpcl divide by zero
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.9 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in OpenJPEG up to 2.3.0 and classified as problematic. This vulnerability affects the function pi_next_pcrl/pi_next_cprl/pi_next_rpcl of the file openmj2/pi.c. This manipulation causes divide by zero.
The identification of this vulnerability is CVE-2018-20845. It is possible to initiate the attack remotely. There is no exploit available.
Details
A vulnerability classified as problematic was found in OpenJPEG up to 2.3.0 (Image Processing Software). Affected by this vulnerability is the function pi_next_pcrl/pi_next_cprl/pi_next_rpcl of the file openmj2/pi.c. The manipulation with an unknown input leads to a divide by zero vulnerability. The CWE definition for the vulnerability is CWE-369. The product divides a value by zero. As an impact it is known to affect availability. The summary by CVE is:
Division-by-zero vulnerabilities in the functions pi_next_pcrl, pi_next_cprl, and pi_next_rpcl in openmj2/pi.c in OpenJPEG through 2.3.0 allow remote attackers to cause a denial of service (application crash).
The weakness was shared 06/26/2019 (Website). The advisory is shared at securityfocus.com. This vulnerability is known as CVE-2018-20845 since 06/26/2019. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1499 for this issue.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The entries VDB-136910 and VDB-136911 are related to this item. 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.9VulDB Meta Temp Score: 5.9
VulDB Base Score: 5.3
VulDB Temp Score: 5.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: Divide by zeroCWE: CWE-369 / 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: 🔍
Patch: github.com
Timeline
06/26/2019 🔍06/26/2019 🔍
06/27/2019 🔍
10/08/2023 🔍
Sources
Advisory: securityfocus.com⛔Status: Not defined
CVE: CVE-2018-20845 (🔍)
GCVE (CVE): GCVE-0-2018-20845
GCVE (VulDB): GCVE-100-136909
SecurityFocus: 108921
See also: 🔍
Entry
Created: 06/27/2019 08:51Updated: 10/08/2023 10:01
Changes: 06/27/2019 08:51 (55), 06/28/2020 06:45 (1), 10/08/2023 10:01 (4)
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.