| Bug #34575 | SQL_C_CHAR value type and numeric parameter type causes trouble | ||
|---|---|---|---|
| Submitted: | 15 Feb 2008 2:12 | Modified: | 14 Mar 2008 19:37 |
| Reporter: | Jim Winstead | ||
| Status: | Closed | ||
| Category: | Connector/ODBC | Severity: | S3 (Non-critical) |
| Version: | 3.51 | OS: | Any |
| Assigned to: | Jim Winstead | Target Version: | 3.51 |
[15 Feb 2008 2:12]
Jim Winstead
[15 Feb 2008 2:14]
Jim Winstead
Fix handling of SQL_C_CHAR being passed as numeric parameters
Attachment: bug34575.patch (text/plain), 5.22 KiB.
[13 Mar 2008 19:15]
Jim Winstead
Updated test
Attachment: bug34575.patch (text/plain), 5.22 KiB.
[13 Mar 2008 22:35]
Jim Winstead
The fix for this bug has been committed, and will be in 3.51.24.
[14 Mar 2008 19:37]
MC Brown
A note has been added to the 3.51.24 changelog: Security Enhancement: Accessing a parameer with the type of SQL_C_CHAR, but with a numeric type and a length of zero, the parameter marker would get stropped from the query. In addition, a SQL injection was possible if the parameter value had a non-zero length and was not numeric, the text would be inserted verbatim.
