Bug 2005477 (CVE-2020-21533)

Summary:	CVE-2020-21533 transfig: stack-based buffer overflow in the read_textobject() in read.c
Product:	[Other] Security Response	Reporter:	Guilherme de Almeida Suckevicz <gsuckevi>
Component:	vulnerability	Assignee:	Nobody <nobody>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	databases-maint, hhorak, kasal, mschorm, pkubat
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:	In transfig's fig2dev 3.2.7b it is possible for an attacker to create a specially crafted file that causes a buffer overflow due to the usage of fgets. This leads to a denial of service, impacting availability of the program.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-12-13 13:40:32 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	2005921
Bug Blocks:	2005482

Description Guilherme de Almeida Suckevicz 2021-09-17 18:19:00 UTC

fig2dev 3.2.7b contains a stack buffer overflow in the read_textobject function in read.c.

Reference:
https://sourceforge.net/p/mcj/tickets/59/

Comment 1 Garrett Tucker 2021-09-20 13:43:22 UTC

After analysis of this flaw, all versions of RHEL 8 are affected. RHEL 9 remains unaffected as the patch to fix this flaw was applied and introduced in RHEL 9. The patch applied is: https://sourceforge.net/p/mcj/fig2dev/ci/41b9bb838a3d544539f6e68aa4f87d70ef7d45ce/. This flaw was caused by the use of fgets which led to a buffer overflow and segmentation fault in read_objects when a specially crafted file was used as input to the program.

Comment 3 Garrett Tucker 2021-10-19 17:11:48 UTC

Analysis did not show any sign of being able to achieve code execution with this flaw. The flaw present caused a denial of service to the program affecting availability, but with no found effects on Integrity or Confidentiality of data. As such the CVSS score should be 5.5/CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H