Jet 4.0 Text IISAM Allows Users to Append Lines to System Files

The Text IISAM allows you to manipulate text files without checking the file name extension. This creates a potential security risk because it can be used to read or write to a system text file.

The Text IISAM is able to modify the contents of text files that are formatted as data tables. This feature makes it easy for you to exchange data on different systems.

This problem has been fixed in the latest edition of the Jet Service Pack. The following registry key is dynamically added when a program loads the Text IISAM. This registry key prevents this type of security risk: For additional information about how to obtain the latest version of the Jet 4.0 database engine, click the following article number to view the article in the Microsoft Knowledge Base:

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

NOTE: Jet40SP3.exe was updated on October 11, 1999. If you previously installed this update and would like to use the stricter security control provided in the updated Mstext40.dll, run the installed Mstext40.reg file. To run the Mstext40.reg file, locate the file on your system and double-click it.

There could be a possible security risk when someone uses the Text IISAM to modify any of the system text files, such as Autoexec.bat, Config.sys, System.ini, and so on.

After you install the updated version of Jet, you will only be able to use the Text IISAM to update text files with the following extensions:

• txt
• csv
• tab
• asc
• htm
• html

These are the default extensions that are added to the registry key listed in the "Resolution" section. The Value data for the registry key is: In the first release of Jet 4.0 SP3, you were not be able to use the Text IISAM to update text files with the following extensions:

• bat
• cmd
• ini
• sys
• inf
• vbs
• js

These are the default extensions that were added to the registry key listed in the "Resolution" section with the first release of Jet 4.0 SP3. The Value data for the registry key was: NOTE: The first release of Jet 4.0 SP3 did not provide the use of an exclamation mark (!). When you place an exclamation mark at the beginning of the Value data, you can modify only files with the extensions listed. When you do not place an exclamation mark at the beginning of the Value data, you cannot modify files with the extension listed. With the Jet 4.0 Text IISAM, you cannot set the registry key to an empty string. Therefore, if you do not want to block access to any system text files, you should set the registry key to a binary file name extension. For example, you can use .exe.

NOTE: Microsoft Access users may receive the following error when trying to import a text file that is not one of the enabled extensions: To resolve the error, either rename the file extension to one of the enabled extension types or modify the DisabledExtensions registry key using the methods in this article.