Bug 1126272 - mysql: yaSSL off-by-one when decoding dates form X.509 certificates
Summary: mysql: yaSSL off-by-one when decoding dates form X.509 certificates
Alias: None
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
Depends On:
Blocks: 1126275
TreeView+ depends on / blocked
Reported: 2014-08-04 04:18 UTC by Murray McAllister
Modified: 2021-02-17 06:20 UTC (History)
8 users (show)

Fixed In Version: mysql 5.5.39, mysql 5.6.20
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2014-08-04 07:04:02 UTC

Attachments (Terms of Use)

Description Murray McAllister 2014-08-04 04:18:27 UTC
The MySQL 5.5.39 and 5.6.20 releases fix an unspecified certificate decoding issue in yaSSL:

"yaSSL code had an off-by-one error in certificate decoding that could cause buffer overflow."



Comment 1 Murray McAllister 2014-08-04 04:21:06 UTC
Created mariadb tracking bugs for this issue:

Affects: fedora-all [bug 1126274]

Comment 2 Murray McAllister 2014-08-04 04:21:09 UTC
Created community-mysql tracking bugs for this issue:

Affects: fedora-all [bug 1126273]

Comment 3 Tomas Hoger 2014-08-04 07:04:02 UTC
MySQL upstream commit:

This fixes an off-by-one issue in the handling of validity start and end dates in X.509 certificates.  Value written past the end of buffer is '\0'.  Additionally, overwrite should only clobber other members of the CertDecoder class, hence it does not seem this should lead to direct code execution.  However, as it might lead to overwrite of verify_ field, it may lead to bypass of certificate verification.

MySQL and MariaDB packages shipped in Red Hat products and Fedora use system OpenSSL library to implement TLS/SSL.  Embedded yaSSL is not used, hence those packages are not affected by this issue.


Not vulnerable.  This issue did not affect the versions of MySQL and MariaDB as shipped with Red Hat Enterprise Linux 5, 6, and 7, and Red Hat Software Collections 1.

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