libwebp up to 1.0.0 WebPDecodeRGBInto heap-based overflow

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

Summaryinfo

A vulnerability was found in libwebp up to 1.0.0. It has been classified as critical. This issue affects the function WebPDecodeRGBInto. Performing a manipulation results in heap-based overflow. This vulnerability is cataloged as CVE-2020-36328. There is no exploit available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability classified as critical has been found in libwebp up to 1.0.0. This affects the function WebPDecodeRGBInto. The manipulation with an unknown input leads to a heap-based overflow vulnerability. CWE is classifying the issue as CWE-122. A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc(). This is going to have an impact on confidentiality, integrity, and availability.

The weakness was shared 05/22/2021. The advisory is shared at bugzilla.redhat.com. This vulnerability is uniquely identified as CVE-2020-36328. Technical details are known, but no exploit is available.

The vulnerability scanner Nessus provides a plugin with the ID 208636 (CentOS 7 : libwebp (RHSA-2021:2260)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 1.0.1 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at Tenable (208636). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.5
VulDB Meta Temp Score: 5.3

VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

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

Exploitinginfo

Class: Heap-based overflow
CWE: CWE-122 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Partially

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 208636
Nessus Name: CentOS 7 : libwebp (RHSA-2021:2260)

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: libwebp 1.0.1

Timelineinfo

05/04/2021 🔍
05/22/2021 +18 days 🔍
05/22/2021 +0 days 🔍
10/12/2024 +1239 days 🔍

Sourcesinfo

Advisory: bugzilla.redhat.com
Status: Confirmed

CVE: CVE-2020-36328 (🔍)
GCVE (CVE): GCVE-0-2020-36328
GCVE (VulDB): GCVE-100-175509

Entryinfo

Created: 05/22/2021 13:29
Updated: 10/12/2024 08:50
Changes: 05/22/2021 13:29 (37), 05/23/2021 19:17 (5), 10/12/2024 08:50 (16)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to stay up to date on a daily basis?

Enable the mail alert feature now!