libsixel 1.8.6 sixel_encoder_encode_bytes buffer overflow

EntryeditHistoryDiffjsonxmlCTI
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.
3.5$0-$5k0.00

A vulnerability was found in libsixel 1.8.6. It has been declared as problematic. This vulnerability affects the function sixel_encoder_encode_bytes. The manipulation with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is CWE-120. As an impact it is known to affect availability. CVE summarizes:

Buffer Overflow in the "sixel_encoder_encode_bytes" function of Libsixel v1.8.6 allows attackers to cause a Denial of Service (DoS).

The weakness was disclosed 04/15/2021. The advisory is shared for download at github.com. This vulnerability was named CVE-2020-36120 since 01/04/2021. The exploitation appears to be easy. Access to the local network is required for this attack to succeed. Required for exploitation is a single authentication. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 04/17/2021).

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

Productinfoedit

Name

CPE 2.3infoedit

CPE 2.2infoedit

CVSSv3infoedit

VulDB Meta Base Score: 3.5
VulDB Meta Temp Score: 3.5

VulDB Base Score: 3.5
VulDB Temp Score: 3.5
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2infoedit

AVACAuCIA
🔍🔍🔍🔍🔍🔍
🔍🔍🔍🔍🔍🔍
🔍🔍🔍🔍🔍🔍
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
unlockunlockunlockunlockunlockunlock
unlockunlockunlockunlockunlockunlock
unlockunlockunlockunlockunlockunlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfoedit

Class: Memory corruption
CWE: CWE-120
ATT&CK: Unknown

Local: No
Remote: Partially

Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒

0-Dayunlockunlockunlockunlock
Todayunlockunlockunlockunlock

Threat Intelligenceinfoedit

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

Countermeasuresinfoedit

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔒

Timelineinfoedit

01/04/2021 CVE assigned
04/15/2021 +100 days Advisory disclosed
04/15/2021 +0 days VulDB entry created
04/17/2021 +2 days VulDB last update

Sourcesinfoedit

Advisory: github.com
Status: Not defined

CVE: CVE-2020-36120 (🔒)

Entryinfoedit

Created: 04/15/2021 10:38 AM
Updated: 04/17/2021 09:09 PM
Changes: (2) source_cve_assigned source_cve_nvd_summary
Complete: 🔍

Comments

No comments yet. Languages: . Please log in to comment.

Do you need the next level of professionalism?

Upgrade your account now!