libsixel up to 1.8.2 frompnm.c load_pnm operation after expiration

HistoryDiffrelatejsonxmlCTI

CVSS Meta Temp Score CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.	Current Exploit Price (≈) Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.	CTI Interest Score Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
6.3	$0-$5k	0.00

Summaryinfo

A vulnerability labeled as problematic has been found in libsixel up to 1.8.2. This impacts the function load_pnm of the file frompnm.c. Such manipulation leads to operation after expiration. This vulnerability is traded as CVE-2019-20022. The attack may be launched remotely. There is no exploit available. The affected component should be upgraded.

Detailsinfo

A vulnerability was found in libsixel up to 1.8.2 and classified as critical. Affected by this issue is the function load_pnm of the file frompnm.c. The manipulation with an unknown input leads to a operation after expiration vulnerability. Using CWE to declare the problem leads to CWE-672. The product uses, accesses, or otherwise operates on a resource after that resource has been expired, released, or revoked. Impacted is availability. CVE summarizes:

An invalid memory address dereference was discovered in load_pnm in frompnm.c in libsixel before 1.8.3.

The weakness was shared 12/27/2019. This vulnerability is handled as CVE-2019-20022 since 12/27/2019. The attack may be launched remotely. No form of authentication is required for exploitation. Successful exploitation requires user interaction by the victim. Technical details are known, but there is no available exploit.

Upgrading to version 1.8.3 eliminates this vulnerability.

The entries VDB-147796 and VDB-147795 are related to this item. If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Name

libsixel

Version

License

open-source

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.5
VulDB Meta Temp Score: 6.3

VulDB Base Score: 6.5
VulDB Temp Score: 6.2
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 6.5
NVD Vector: 🔍

CVSSv2info

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: 🔍

Exploitinginfo

Class: Operation after expiration
CWE: CWE-672
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 Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: libsixel 1.8.3

Timelineinfo

12/27/2019 🔍
12/27/2019 +0 days 🔍
12/27/2019 +0 days 🔍
03/17/2024 +1542 days 🔍

Sourcesinfo

Advisory: 108
Status: Not defined

CVE: CVE-2019-20022 (🔍)
GCVE (CVE): GCVE-0-2019-20022
GCVE (VulDB): GCVE-100-147794
See also: 🔍

Entryinfo

Created: 12/27/2019 09:04
Updated: 03/17/2024 14:13
Changes: 12/27/2019 09:04 (38), 12/27/2019 09:09 (17), 03/17/2024 14:13 (5)
Complete: 🔍
Cache ID: 216::103

If you want to get best quality of vulnerability data, you may have to visit VulDB.