Bug 756947 - Defects like cut/paste errors, NULL dereference or missing brake stmts (mysql-connector-odbc)
Summary: Defects like cut/paste errors, NULL dereference or missing brake stmts (mysql...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: mysql-connector-odbc
Version: 5.8
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Tom Lane
QA Contact: qe-baseos-daemons
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-25 09:23 UTC by Pavel Raiskup
Modified: 2013-03-06 04:01 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-03-06 04:01:52 UTC
Target Upstream Version:


Attachments (Terms of Use)
fixes for the most obvious errors (3.38 KB, patch)
2011-12-19 17:14 UTC, Honza Horak
no flags Details | Diff

Description Pavel Raiskup 2011-11-25 09:23:47 UTC
1) Possible null dereference in "insert_param()"

   => mysql-connector-odbc-3.51.26r1127/driver/execute.c:330|334|...|427

   It may be an unrealistic condition to be the variable param->buffer equal
   to NULL (line 258) but if yes, this case should be properly handled.
   Callers of "insert_param()" are checking for zero-value also, should not
   there be on line 286 something like this only?

 | @@ -283,6 +283,7 @@ char *insert_param(DBC *dbc, char *to,PARAM_BIND *param)
 |          else
 |          {
 |              length= 0;     /* This is actually an error */
 | +            return 0;
 |          }
 |      }
 |      else if ( *(param->actual_len) == SQL_NULL_DATA )

2) Missing my_malloc return check

   => mysql-connector-odbc-3.51.26r1127/driver/cursor.c:332

3) Copy and paste error?

   => util/MYODBCUtilWriteDataSourceStr.c:71

   Passing possible NULL pointer -- pDataSource->pszDATABASE -- into
   MYODBCUtilInsertStr(). Shouldn't there be the pDataSource->pszDESCRIPTION
   pointer?

4) Missing break statements

   I'm not sure about these defects .. it is usually not obvious if it is real
   or not. It would be good if somebody who is more involved in this tool
   could look at these..

   => installer/myodbc3i.c:552
   => installer/myodbc3i.c:738
   => installer/myodbc3i.c:747

These problems were found in RHEL 5.8 by the Coverity tool. I've tried to
keep only most serious looking ones.

Comment 2 Pavel Raiskup 2011-11-25 09:51:54 UTC
This report was meant just for consideration, I don't insist on that anything has to be repaired.

Comment 3 Tom Lane 2011-11-25 16:09:56 UTC
It would be best to file this upstream (i.e., at bugs.mysql.com).  I don't know this code well enough to evaluate anything subtle.  (Although really they're not going to be very interested in reports against 3.51.26 ... have you tried a coverity run against current Fedora, which is 5.1.8?)

Comment 4 Ondrej Vasik 2011-11-25 17:10:26 UTC
Yes, Fedora Rawhide scan of RHEL set of packages was done as well, recent results from F17 will be available soon. (including 5.1.8).

Actually this one bugzilla was reported a bit accidently - Pavel did the full review as he thought that this is new package. As he filtered the false positives and prepared the list of most serious potential defects, I recommended him to report that for consideration by maintainer. Sorry for disturbing you.

Feel free to close this bug WONTFIX, as these defects are not new and we are quite late in RHEL-5 release cycle.

Comment 9 RHEL Program Management 2012-01-09 14:48:42 UTC
This request was evaluated by Red Hat Product Management for inclusion in Red Hat Enterprise Linux 5.8 and Red Hat does not plan to fix this issue the currently developed update.

Contact your manager or support representative in case you need to escalate this bug.

Comment 11 RHEL Program Management 2012-06-12 01:30:36 UTC
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated in the
current release, Red Hat is unfortunately unable to address this
request at this time. Red Hat invites you to ask your support
representative to propose this request, if appropriate and relevant,
in the next release of Red Hat Enterprise Linux.

Comment 12 Tom Lane 2013-03-06 04:01:52 UTC
Filed upstream by Honza; closing this bug WONTFIX per comment #4.


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