Fix GH-22668: odbc heap over-read on oversized column value#22670
Open
iliaal wants to merge 1 commit into
Open
Fix GH-22668: odbc heap over-read on oversized column value#22670iliaal wants to merge 1 commit into
iliaal wants to merge 1 commit into
Conversation
| --SKIPIF-- | ||
| <?php | ||
| $file = tempnam(sys_get_temp_dir(), "gh22668"); | ||
| $conn = @odbc_connect("Driver=SQLite3;Database=$file", null, null); |
Member
There was a problem hiding this comment.
Again, see if we can use SQL Server, if possible to reproduce it if not, :memory: and we'll have to figure out adding it to CI
Contributor
Author
There was a problem hiding this comment.
Checked ext/odbc against the 2022 container directly, same as #22672: it doesn't reproduce. SQL Server reports a field length >= the value (VARCHAR(50) -> 50), or 0/INT_MAX for LOB types which take the long-column path, never a short display size against an over-long value. Switched the test to :memory:. If you'd rather it run than skip, I'll add the SQLite ODBC driver to CI, which covers #22672 as well.
ext/odbc bound a displaysize+1 buffer per column but built the result string from the driver-reported vallen. A conforming driver truncates an over-long value into the buffer yet reports the full length, so the fetch over-read past the allocation and returned adjacent heap bytes to userland. Store the bound capacity in odbc_result_value and clamp the string length to it at the three bound-buffer fetch sites (odbc_fetch_array/object, odbc_fetch_into, odbc_result); the SQLGetData long-column paths stay bounded by longreadlen. Fixes phpGH-22668
c542fb9 to
7e3c4e5
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
ext/odbc builds the result string from the driver-reported vallen, which on truncation exceeds the bound displaysize+1 buffer (SQL_SUCCESS_WITH_INFO), over-reading heap into the returned value. Clamps the length to the bound capacity at the three fetch sites. Reproduces with the SQLite3 ODBC driver; the test skips without it.
Fixes #22668