bug(bq_driver): SQLDriverConnectW corrupts/fails to NUL-terminate outConnectionString (breaks Microsoft Excel / iODBC on macOS)
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
Start in google/cloud/odbc/bq_driver/odbc_api.cc at SQLDriverConnectW and compare its output handling with SQLBrowseConnectW. Check the wire buffer helpers in odbc_type_utils.h and the ODBC truncation behavior described in the issue. Done means using separate UTF-8 storage, respecting the wide output buffer limit, and ensuring the result is NUL-terminated; the issue also requests updating the macOS release tarball after a new release tag.
由索引模型根据 Issue 内容生成。
描述
Summary
When using the Google BigQuery ODBC Driver on macOS with iODBC (sizeof(SQLWCHAR) == 4) and Microsoft Excel / Microsoft Query, calling SQLDriverConnectW corrupts outConnectionString (szConnStrOut), causing Excel's Return Data action (inserting query results as a Table or PivotTable) to fail with:
[iODBC][Driver Manager]Data source name not found and no default driver specified. Driver could not be loaded
Root Cause Analysis
1. Latest Published Release (v1.3.1 / ODBCDriverforBigQuery_macos_latest.tar.gz)
In v1.3.1 (currently the latest binary published on GCS bq-driver-releases and GitHub Releases), SQLDriverConnectW in google/cloud/odbc/bq_driver/odbc_api.cc passed reinterpret_cast<SQLCHAR*>(outConnectionString) to SQLDriverConnectInternal() (which wrote 8-bit UTF-8 bytes into the caller's SQLWCHAR* buffer) and then executed:
outConnectionString = ToSqlWChar(utf16_out_conn_str->data());
Because outConnectionString is a pointer passed by value, reassigning the local parameter was a dead store (optimized out under -O3) and never copied the converted wide characters back into the caller's buffer. Consequently:
outConnectionStringstill contained raw 8-bit UTF-8 bytes (e.g.,"DSN=my-bq-dsn;").- On macOS,
iODBCreadsoutConnectionStringas 32-bitwchar_t(UTF-32LE) code units (0x3d4e5344, ...) and converts them into"??????". - When clicking Return Data in Microsoft Query on macOS,
Microsoft Query.apppassesOutConnectionStringtoMicrosoft Excel.appto open the worksheet connection, which immediately fails iniODBC.
2. Remaining Issues on main (google/cloud/odbc/bq_driver/odbc_api.cc:274-300)
Commit d080bdb282 (#1506) replaced the dead pointer assignment with:
WriteWideToWireBuffer(*utf16_out_conn_str, outConnectionString,
out_conn_str_len);
However, three issues remain in SQLDriverConnectW on main:
- Missing wire
NULterminator:WriteWideToWireBufferdefaults tobool null_terminate = false(odbc_type_utils.h:188), and unlikeSQLBrowseConnectW(odbc_api.cc:402),SQLDriverConnectWneither zerosoutConnectionStringbeforehand nor passes/*null_terminate=*/true. - Buffer overflow when
outConnectionStringBufferLentruncates the output: Per the ODBC specification,PopulateOutputConnectionStringsets*out_conn_str_lento the full untruncated string length even whenout_conn_str_buflenis smaller (SQL_SUCCESS_WITH_INFO/01004). Passingout_conn_str_lendirectly toWriteWideToWireBufferwithout clamping tooutConnectionStringBufferLen - 1writes past the end ofoutConnectionString, andUtf8ToUtf16((char*)out_conn_str)on line 287 ignoreselseonly becauseout_conn_str_len > 0. - Aliasing
outConnectionStringas a temporary UTF-8 buffer: CastingoutConnectionString(SQLWCHAR*) directly toSQLCHAR*aliases the caller's output buffer before wide conversion.
Proposed Fix (google/cloud/odbc/bq_driver/odbc_api.cc)
Use a separate temporary std::vector<SQLCHAR> buffer for SQLDriverConnectInternal, clamp the number of wide characters written to outConnectionStringBufferLen - 1, and pass /*null_terminate=*/true to WriteWideToWireBuffer:
std::vector<SQLCHAR> utf8_out_buf(
outConnectionString && outConnectionStringBufferLen > 0
? static_cast<size_t>(outConnectionStringBufferLen)
: 0,
0);
SQLCHAR* out_conn_str =
(!utf8_out_buf.empty()) ? utf8_out_buf.data() : nullptr;
SQLSMALLINT out_conn_str_len = 0;
rc = google::cloud::odbc_bq_driver::SQLDriverConnectInternal(
connectionHandle, windowHandle, sqlchar_in_connection_str,
inConnectionStringLen, out_conn_str, outConnectionStringBufferLen,
&out_conn_str_len, driverCompletion);
// Handle Unicode conversion of output parameters.
if (SQL_SUCCEEDED(rc) && outConnectionString) {
if (outConnectionStringBufferLen > 0) {
std::string val(ToCharStr(out_conn_str));
StatusRecordOr<std::wstring> utf16_out_conn_str = Utf8ToUtf16(val);
if (!utf16_out_conn_str) {
return utf16_out_conn_str.GetCalculatedReturnCode();
}
size_t const max_chars =
static_cast<size_t>(outConnectionStringBufferLen - 1);
size_t const to_copy =
std::min<size_t>(utf16_out_conn_str->size(), max_chars);
WriteWideToWireBuffer(*utf16_out_conn_str, outConnectionString, to_copy,
/*null_terminate=*/true);
} else if (outConnectionStringBufferLen == 0) {
// Buffer length is 0; do not write to outConnectionString.
}
}
if (outConnectionStringLen) *outConnectionStringLen = out_conn_str_len;
(Note: Once a new release tag is cut, please also update the macOS tarball at https://storage.googleapis.com/bq-driver-releases/odbc/ODBCDriverforBigQuery_macos_latest.tar.gz, which currently still serves v1.3.1.)
- 主要语言
- C++
- 星标
- 5
- 派生
- 8
- 平均合并
- 2 天 14 小时
- 30 天内合并 PR
- 10
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
googleapis/cpp-bigquery-odbc 的其他 Issue
-
priority: p2 type: bug
难度 4/5 3-5 天 新手友好度 35/100
googleapis/cpp-bigquery-odbc#1686 · 1 条评论 ·
维护者通常 1 天内回复
-
Statement execution integration tests refactor可能重新可做 @sachinpro 于 977 天前认领,目前没有进行中的 PR。 未关闭priority: p2 type: bug
googleapis/cpp-bigquery-odbc#271 · 已指派 1 人 ·
维护者通常 1 天内回复
-
priority: p2 type: bug
难度 2/5 1-3 小时 新手友好度 35/100
googleapis/cpp-bigquery-odbc#215 ·
维护者通常 1 天内回复
-
Remove external dependencies from Unit Tests可能重新可做 @sachinpro 于 1033 天前认领,目前没有进行中的 PR。 未关闭priority: p2 type: bug
googleapis/cpp-bigquery-odbc#195 · 已指派 1 人 ·
维护者通常 1 天内回复
-
priority: p2 type: cleanup
难度 4/5 3-5 天 新手友好度 35/100
googleapis/cpp-bigquery-odbc#187 ·
维护者通常 1 天内回复
查看 googleapis/cpp-bigquery-odbc 的全部 Issue
相似的 Issue
-
audit-reference-check
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 76/100
schrodinger/pymol-open-source#532 ·
-
难度 2/5 1-3 小时 新手友好度 70/100
-
难度 1/5 1 小时以内 新手友好度 83/100
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 82/100
维护者通常 1 天内回复