Bug 1467600 (CVE-2017-10788)

Summary:	CVE-2017-10788 perl-DBD-MySQL: Use-after-free when calling mysql_stmt_error() after mysql_stmt_close()
Product:	[Other] Security Response	Reporter:	Adam Mariš <amaris>
Component:	vulnerability	Assignee:	Red Hat Product Security <security-response-team>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	hhorak, jorton, jplesnik, perl-devel, perl-maint-list, ppisar, psabata, sardella
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:	2017-08-31 08:40:19 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:	1467608
Bug Blocks:	1467607

Description Adam Mariš 2017-07-04 10:20:25 UTC

The DBD::mysql module through 4.043 for Perl allows remote attackers to cause a denial of service (use-after-free and application crash) or possibly have unspecified other impact by triggering (1) certain error responses from a MySQL server or (2) a loss of a network connection to a MySQL server. The use-after-free defect was introduced by relying on incorrect Oracle mysql_stmt_close documentation and code examples.

Upstream bug:

https://github.com/perl5-dbi/DBD-mysql/issues/120

References:

http://seclists.org/oss-sec/2017/q2/443

Comment 1 Adam Mariš 2017-07-04 10:39:16 UTC

Created perl-DBD-MySQL tracking bugs for this issue:

Affects: fedora-all [bug 1467608]

Comment 3 Stefan Cornelius 2017-08-25 15:16:55 UTC

Patch:
https://github.com/perl5-dbi/DBD-mysql/files/1116951/0001-Fix-use-after-free-after-calling-mysql_stmt_close.patch.txt

Comment 4 Stefan Cornelius 2017-08-31 08:39:48 UTC

Statement:

Red Hat Product Security has rated this issue as having Moderate security impact. This issue is not currently planned to be addressed in future updates. For additional information, refer to the Issue Severity Classification: https://access.redhat.com/security/updates/classification/.