Bug 1467600 - (CVE-2017-10788) CVE-2017-10788 perl-DBD-MySQL: Use-after-free when calling mysql_stmt_error() after mysql_stmt_close()
CVE-2017-10788 perl-DBD-MySQL: Use-after-free when calling mysql_stmt_error()...
Status: CLOSED WONTFIX
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
impact=moderate,public=20170608,repor...
: Security
Depends On: 1467608
Blocks: 1467607
  Show dependency treegraph
 
Reported: 2017-07-04 06:20 EDT by Adam Mariš
Modified: 2017-08-31 04:40 EDT (History)
8 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-08-31 04:40:19 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Adam Mariš 2017-07-04 06:20:25 EDT
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 06:39:16 EDT
Created perl-DBD-MySQL tracking bugs for this issue:

Affects: fedora-all [bug 1467608]
Comment 4 Stefan Cornelius 2017-08-31 04:39:48 EDT
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/.

Note You need to log in before you can comment on or make changes to this bug.