Category: Vulnerability - Warning Incident ID: X000801 Priority: 3 - Non-Critical Status: Investigate Further and Document Component:
ODMA32.dll, all current versions up to 2.0.0
- Repaired in: none
- Related information:
Assigned To: Dennis E. Hamilton Reported By:
Dennis Hamilton 2000-08-04
Date Opened: 2000-08-04 Date Closed: none
An application that uses the ODMA API incorrectly can induce a crash in any version of
ODMA32.dll, the Connection Manager for Win32. No direct damage occurs, but users will lose any work in progress and the DMS being used may have incomplete materials in its collection.
There are no reported production incidents attributable to this particular defect. It is documented as a warning for future trouble-shooting and for maintenance of Connection Manager implementations.
This condition is most likely to occur in development or maintenance of an ODMA-aware application. The conditions necessary to provoke the crash are unlikely in well-behaved applications in production usage.
The ODMA Connection Manager must examine the ODMA Document IDs that are provided as parameters for a number of ODMA 2.0 API functions. This is necessary to determine the DMS ID of the DMS Integration to use in the operation.
In the cases where the Document ID parameter is not optional, the ODMA Connection Manager 1.0.0, 1.5.0, and 2.0.0 implementations all fail to defend against erroneous
NULLvalues for an
lpszDocIdparameter before using its value.
ODMA32.dllwill terminate with a fatal error when it receives a
NULLvalue in any operation having a required
lpszDocIdparameter. This is the result of performing
ODMClient::ConnectDocIdof Connection Manager module
Odma.dllwill operate successfully, providing an appropriate
ODMSTATUSerror code. This is because
*NULLis arranged to be
0on MS-DOS and Win16, so that the result of
strlen(NULL)is the same as
- Identify and report those ODMA Connection Manager functions that fail to defend against
- Confirm that
strlen(NULL)is not well-defined for ANSI Standard C and that
strlen(NULL)fails for a number of ANSI Standard C
- Demonstrate that this failure actually occurs with the current ODMA 2.0 connection manager implementation,
- Describe appropriate work-around and safeguard techniques.
- Schedule correction in the next rebuild of ODMA Connection Manager implementations.
Please provide any relevant information and feedback to the ODMA Tech List or directly to the AIIM DMware Technical Coordinator.
created 2000-08-04-13:47 -0700 (pdt) by orcmid
$$Author: Orcmid $
$$Date: 00-08-07 14:44 $
$$Revision: 5 $