KImageFormats up to 5.81.0 loadTileRLE stack-based overflow

Summaryinfo

A vulnerability described as critical has been identified in KImageFormats up to 5.81.0. This impacts the function XCFImageFormat::loadTileRLE. Executing a manipulation can lead to stack-based overflow. This vulnerability appears as CVE-2021-36083. There is no available exploit. It is advisable to implement a patch to correct this issue.

Detailsinfo

A vulnerability classified as critical was found in KImageFormats up to 5.81.0. This vulnerability affects the function XCFImageFormat::loadTileRLE. The manipulation with an unknown input leads to a stack-based overflow vulnerability. The CWE definition for the vulnerability is CWE-121. A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function). As an impact it is known to affect confidentiality, integrity, and availability.

The weakness was presented 07/01/2021. The advisory is shared for download at bugs.chromium.org. This vulnerability was named CVE-2021-36083. There are known technical details, but no exploit is available.

Applying a patch is able to eliminate this problem. The bugfix is ready for download at invent.kde.org.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Name

• KImageFormats

Version

• 5.0
• 5.1
• 5.2
• 5.3
• 5.4
• 5.5
• 5.6
• 5.7
• 5.8
• 5.9
• 5.10
• 5.11
• 5.12
• 5.13
• 5.14
• 5.15
• 5.16
• 5.17
• 5.18
• 5.19
• 5.20
• 5.21
• 5.22
• 5.23
• 5.24
• 5.25
• 5.26
• 5.27
• 5.28
• 5.29
• 5.30
• 5.31
• 5.32
• 5.33
• 5.34
• 5.35
• 5.36
• 5.37
• 5.38
• 5.39
• 5.40
• 5.41
• 5.42
• 5.43
• 5.44
• 5.45
• 5.46
• 5.47
• 5.48
• 5.49
• 5.50
• 5.51
• 5.52
• 5.53
• 5.54
• 5.55
• 5.56
• 5.57
• 5.58
• 5.59
• 5.60
• 5.61
• 5.62
• 5.63
• 5.64
• 5.65
• 5.66
• 5.67
• 5.68
• 5.69
• 5.70
• 5.71
• 5.72
• 5.73
• 5.74
• 5.75
• 5.76
• 5.77
• 5.78
• 5.79
• 5.80
• 5.81.0

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion