Vulnerability Note VU#176380

Microsoft Jet Database Engine fails to properly validate Access database files

Original Release date: 03 Oct 2005 | Last revised: 03 Oct 2005

Overview

A vulnerability in the Microsoft Jet database engine could allow a remote attacker to execute code of their choice on a vulnerable system.

Description

The Microsoft Jet Database Engine (Jet) provides data access functionality to a number of other Microsoft and many third party applications. An input validation error in the way that the Jet engine library handles the database files used by Microsoft Access (.mdb files) results in a vulnerability that could allow a remote attacker to execute code on a vulnerable system. In order to exploit this vulnerability, the attacker would need the ability to supply a specially crafted .mdb file and coax or trick a user into opening it. The malicious .mdb file could be supplied remotely by a number of methods including, but not limited to, a web page, an email message, or a shared network folder.

Impact

A remote, unauthenticated attacker with the ability to supply a specially crafted .mdb file could execute code of their choice on a vulnerable system. The attacker-supplied code would be executed with the same privileges as the user context of the application using the Jet Database Engine.

Solution

The CERT/CC is currently unaware of a practical solution to this problem.

Workarounds

Avoid opening Microsoft Access Database (.mdb) files from untrusted sources.

Systems Affected (Learn More)

No information available. If you are a vendor and your product is affected, let us know.

CVSS Metrics (Learn More)

Group Score Vector
Base N/A N/A
Temporal N/A N/A
Environmental N/A N/A

References

Credit

This vulnerability was originally reported by researchers at HexView.

This document was written by Chad R Dougherty.

Other Information

  • CVE IDs: CAN-2005-0944
  • Date Public: 31 Mar 2005
  • Date First Published: 03 Oct 2005
  • Date Last Updated: 03 Oct 2005
  • Severity Metric: 4.28
  • Document Revision: 10

Feedback

If you have feedback, comments, or additional information about this vulnerability, please send us email.