|  support |  documentation |  report a bug |  advanced search |  search howto |  statistics |  random bug |  login
Bug #74179 Large mysql requests broken after update to 7.0.x
Submitted: 2017-02-27 21:27 UTC Modified: 2017-02-27 21:53 UTC
Avg. Score:5.0 ± 0.0
Reproduced:1 of 1 (100.0%)
Same Version:1 (100.0%)
Same OS:1 (100.0%)
From: nish dot aravamudan at canonical dot com Assigned:
Status: Duplicate Package: MySQL related
PHP Version: 7.0.16 OS: Ubuntu 16.04
Private report: No CVE-ID: None
View Add Comment Developer Edit
Welcome! If you don't have a Git account, you can't do anything here.
You can add a comment by following this link or if you reported this bug, you can edit this bug over here.
Block user comment
Status: Assign to:
Bug Type:
From: nish dot aravamudan at canonical dot com
New email:
PHP Version: OS:


 [2017-02-27 21:27 UTC] nish dot aravamudan at canonical dot com
Original bug report:

Roughly, we produced a security/update update of the PHP7.0 package in Ubuntu which bumped up to 7.0.15. A user reported that this regressed their installation, specifically:

a web application serving rather big binary blobs from a MariaDB table. After the unattended update (7.0.8-0ubuntu0.16.04.3 to 7.0.15-0ubuntu0.16.04.2), the application would routinely break while trying to fetch a >16Mbyte row from the database server.

Requests resulting in a row under 16Mbyte are processed normally, anything above it would return columns in the wrong order, and right around 0xFFFFF2 a null-character (0x00) is inserted into the stream (when the resulting file is compared to one served with the version used previously)


The prior (working) version was 7.0.8 based.

Test script:
The reporter provided a relatively straightforward test case:

- Ubuntu 16.04
- MariaDB Server (not tested on mysql, but I expect similar results)
- php 7.0 (7.0.15)
- phpMyAdmin

MariaDB: max_allowed_packet = 128M
php: post_max_size and upload_max_filesize raised to 128M

Import the some SQL data, for instance:
This will build you a MyISAM table with 4 columns, 3x varchar(1) and 1 longblob. The table will have one big blob in it, with 32Mbyte worth of 0x20 (space)

Downloading the binary through phpMyAdmin on 7.0.15 will produce a file with a null-character inserted at (for my setup) 0xFFFFF6, the rest of the file is as expected.


Add a Patch

Pull Requests

Add a Pull Request


AllCommentsChangesGit/SVN commitsRelated reports
 [2017-02-27 21:39 UTC] spam2 at rhsoft dot net
smells like which was still not fixed with 71.2. / 7.0.16
 [2017-02-27 21:47 UTC]
-Status: Open +Status: Duplicate
 [2017-02-27 21:47 UTC]
This is a duplicate of bug #74021, which was a regression introduced in 7.0.15 (due to an incorrect fix for bug #73800). The issue is fixed by, which will be part of PHP 7.0.17.
 [2017-02-27 21:53 UTC] nish dot aravamudan at canonical dot com
Thank you for the quick responses!
PHP Copyright © 2001-2024 The PHP Group
All rights reserved.
Last updated: Sun Jun 23 11:01:30 2024 UTC