Bug 1595819 (CVE-2018-12713)

Summary:	CVE-2018-12713 gimp: predictable temporary file name in test-xcf.c unit test
Product:	[Other] Security Response	Reporter:	Laura Pardo <lpardo>
Component:	vulnerability	Assignee:	Red Hat Product Security <security-response-team>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	low	Docs Contact:
Priority:	low
Version:	unspecified	CC:	jridky, nphilipp, phracek
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-06-10 10:30:52 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:	1595820, 1595821, 1596112
Bug Blocks:	1595822

Description Laura Pardo 2018-06-27 14:46:43 UTC

A flaw was found in GIMP through 2.10.2 makes g_get_tmp_dir calls to establish temporary filenames, which may result in a filename that already exists, as demonstrated by the gimp_write_and_read_file function in app/tests/test-xcf.c. This might be leveraged by attackers to overwrite files or read file content that was intended to be private.


References:
https://gitlab.gnome.org/GNOME/gimp/issues/1689

Patch:
https://github.com/GNOME/gimp/commit/c21eff4b031acb04fb4dfce8bd5fdfecc2b6524f

Comment 1 Laura Pardo 2018-06-27 14:47:41 UTC

Created gimp tracking bugs for this issue:

Affects: fedora-all [bug 1595820]

Comment 4 Stefan Cornelius 2018-06-28 09:21:10 UTC

Statement:

This issue did affect the versions of gimp as shipped with Red Hat Enterprise Linux 7. However, as this is an issue in a unit test, it is not a problem if you are using the precompiled gimp package. This is only a problem if you recompile gimp using the src.rpm/SPEC file. Even then it's only a problem if you do not make use of isolating build tools like mock, but instead use rpmbuild directly.