Bug 1667239

Summary:	pango_fc_font_key_get_variations(key) causing crash when key is null
Product:	Red Hat Enterprise Linux 7	Reporter:	Andrew Mike <amike>
Component:	pango	Assignee:	Peng Wu <pwu>
Status:	CLOSED ERRATA	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	urgent	Docs Contact:
Priority:	high
Version:	7.6	CC:	alanm, bbarve, desktop-qa-list, jwright, mkolbas, pwu, smaitra, tpelka
Target Milestone:	rc	Keywords:	Desktop, i18n, ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	pango-1.42.4-3.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1685811 1690325 (view as bug list)		Environment:
Last Closed:	2019-08-06 12:38:30 UTC	Type:	Bug
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:
Bug Blocks:	1640542, 1685811, 1690325

Description Andrew Mike 2019-01-17 20:02:56 UTC

Description of problem:
Behavior in pango_fc_font_key_get_variations(key) causes a crash in some applications when the key parameter is NULL due to lack of parameter validation.

Version-Release number of selected component (if applicable):
pango-1.42.4-1.el7

How reproducible:
Unable to reproduce Eclipse or pango-view, but customers have reported issues, and the issue is seen in other distros (see external bug list).

Additional info:
Patch is available upstream:

Fix crash in pango_fc_font_key_get_variations() when key is null (ad92e199) · Commits · GNOME / pango · GitLab
https://gitlab.gnome.org/GNOME/pango/commit/ad92e199f221499c19f22dce7a16e7d770ad3ae7

Comment 2 Peng Wu 2019-01-18 08:49:19 UTC

I just updated pango in Fedora, will check this bug later.

Comment 20 errata-xmlrpc 2019-08-06 12:38:30 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:2044