Re-Release: Unauthorized Access to IIS Servers through ODBC Data Access with RDS
Published: July 19, 1999 | Updated: July 23, 1999
Version: 1.1
Originally Released as MS98-004: July 17, 1998
Re-Released as MS99-025: July 19, 1999
Revised: July 23, 1999
Summary
Microsoft has identified a vulnerability in Microsoft® Data Access Components (MDAC) that could allow a web site visitor to take unauthorized actions on a web site hosted using Internet Information Server. The vulnerability can be eliminated by reconfiguring or removing the affected components of MDAC.
This vulnerability originally was reported in Microsoft Security Bulletin MS98-004, issued July 17, 1998. It was re-released on July 19, 1999, to remind customers of the need to address the vulnerability. It was updated on July 23, 1999, to discuss the need to remove sample files that are affected by the vulnerability, and to clarify that MDAC 2.0 is affected even if deployed as a clean installation.
The RDS DataFactory object, a component of Microsoft Data Access Components (MDAC), exposes unsafe methods. When installed on a system running Internet Information Server 3.0 or 4.0, the DataFactory object may permit an otherwise unauthorized web user to perform privileged actions, including:
Allowing unauthorized users to execute shell commands on the IIS system as a privileged user.
On a multi-homed Internet-connected IIS system, using MDAC to tunnel SQL and other ODBC data requests through the public connection to a private back-end network.
Allowing unauthorized accessing to secured, non-published files on the IIS system.
Affected Software Versions
The vulnerability affects the Microsoft Data Access Components, when installed on a web server running Internet Information Server 3.0 or 4.0. Specifically:
MDAC 1.5 and 2.0 are affected
MDAC 2.1 is affected if installed as an upgrade from a previous version of MDAC, rather than a clean installation
Any version of MDAC is affected if Sample Pages for RDS are installed.
NOTE: Sample Pages for RDS are provided as part of the Windows 4.0 Option Pack and the MDAC 2.0 Software Development Kit. They are not installed by default in the Option Pack, but are installed by default in the MDAC 2.0 SDK.
NOTE: MDAC 1.5 and IIS are installed by default installations of the Windows NT 4.0 Option Pack.
NOTE: IIS can be installed as part of other Microsoft products, such as Microsoft BackOffice and Microsoft Site Server. MDAC can be installed as part of other Microsoft products, such as Visual C and Microsoft Office.
Microsoft Data Access Components (MDAC) is a fully supported set of technologies. If you require technical assistance with this issue, please contact Microsoft Technical Support. For information on contacting Microsoft Technical Support, please see </https:>https:.
Acknowledgments
Microsoft acknowledges Greg Gonzalez of ITE for bringing additional information regarding this vulnerability to our attention, and .Rain.Forest.Puppy for identifying the involvement of Sample Pages for RDS. Microsoft also acknowledges Russ Cooper (NTBugTraq) for his assistance around this issue.
Revisions
July 19, 1999: Bulletin Created as re-release of MS98-004.
July 23, 1999: Bulletin updated to discuss involvement of Sample Pages for RDS, and to clarify status of MDAC 2.0.
THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.
As an Information Security Administrator, you plan and implement information security of sensitive data by using Microsoft Purview and related services. You’re responsible for mitigating risks by protecting data inside collaboration environments that are managed by Microsoft 365 from internal and external threats and protecting data used by AI services. You also implement information protection, data loss prevention, retention, insider risk management, and manage information security alerts and activities.