Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-1999-0364: Microsoft Access 97 stores a database password as plaintext in a foreign mdb, allowing access to dat

0
High
VulnerabilityCVE-1999-0364cve-1999-0364
Published: Fri Jan 01 1999 (01/01/1999, 05:00:00 UTC)
Source: NVD
Vendor/Project: fms_inc.
Product: total_vb_sourcebook

Description

Microsoft Access 97 stores a database password as plaintext in a foreign mdb, allowing access to data.

AI-Powered Analysis

AILast updated: 06/29/2025, 05:09:48 UTC

Technical Analysis

CVE-1999-0364 is a critical vulnerability affecting Microsoft Access 97 and version 6.0 databases, where the database password is stored in plaintext within a foreign .mdb file. This flaw allows an attacker with access to the database file to retrieve the password without any cryptographic barriers, thereby gaining unauthorized access to the database contents. Since the password is stored unencrypted, any user who can obtain the .mdb file can easily extract the password and subsequently access, modify, or exfiltrate sensitive data stored within the Access database. The vulnerability is particularly severe because it requires no authentication or user interaction to exploit; possession of the database file alone is sufficient. The CVSS score of 10.0 reflects the highest severity, indicating complete compromise of confidentiality, integrity, and availability. Although this vulnerability dates back to 1999 and affects legacy software versions, it remains relevant in environments where these outdated Access versions are still in use, especially in legacy systems or archival data stores. No patches or fixes are available, which means mitigation relies on compensating controls and migration strategies.

Potential Impact

For European organizations, the impact of this vulnerability can be significant if legacy Microsoft Access 97 or version 6.0 databases are still in operational use. Confidential business data, customer information, or intellectual property stored in these databases could be exposed if an attacker gains access to the database files. This could lead to data breaches, regulatory non-compliance (e.g., GDPR violations), reputational damage, and potential financial penalties. The ease of exploitation means that insider threats or attackers who gain access to file shares, backups, or removable media could compromise sensitive data without sophisticated tools. Given the high CVSS score, the vulnerability could also facilitate lateral movement within a network if the compromised database contains credentials or configuration data for other systems. Although modern systems have largely moved away from Access 97, some European organizations in sectors such as manufacturing, government, or small-to-medium enterprises may still rely on legacy applications, increasing their risk exposure.

Mitigation Recommendations

Since no patches are available for this vulnerability, European organizations should prioritize the following mitigation strategies: 1) Identify and inventory all Microsoft Access 97 and 6.0 database files in use across the organization. 2) Migrate legacy databases to modern, supported database platforms that implement strong encryption and access controls. 3) Restrict access to legacy database files using strict file system permissions and network segmentation to limit exposure. 4) Encrypt backups and storage media containing these database files to prevent unauthorized access. 5) Implement robust monitoring and auditing of file access to detect suspicious activity involving legacy database files. 6) Educate staff about the risks of using outdated software and the importance of data protection. 7) If migration is not immediately feasible, consider converting Access databases to newer formats that support encryption or applying third-party encryption tools to protect the files at rest. These steps will reduce the risk of unauthorized data disclosure and help comply with data protection regulations.

Need more detailed analysis?Upgrade to Pro Console

Threat ID: 682ca32bb6fd31d6ed7debe0

Added to database: 5/20/2025, 3:43:39 PM

Last enriched: 6/29/2025, 5:09:48 AM

Last updated: 2/3/2026, 8:58:10 PM

Views: 43

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats