Menu

Star on GitHub · 3.2k

CVE-2000-0323

7.6 · HIGH

The Microsoft Jet database engine allows an attacker to modify text files via a database query, aka the "Text I-ISAM" vulnerability.

Published Jul 28, 1999microsoftEPSS 5.54%

Overview

CVE-2000-0323 is a high-severity vulnerability affecting microsoft jet. It was published on July 28, 1999 and has a CVSS 2.0 base score of 7.6 (HIGH).

This vulnerability has a CVSS 2.0 base score of 7.6, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

Technical description

The Microsoft Jet database engine allows an attacker to modify text files via a database query, aka the "Text I-ISAM" vulnerability.

Remediation

Check the references section for vendor advisories and patches from microsoft. Update jet to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Affected products

VendorProductVersionsStatus

Frequently asked questions

What is CVE-2000-0323?

CVE-2000-0323 is a high-severity vulnerability affecting microsoft jet. It was published on July 28, 1999 and has a CVSS 2.0 base score of 7.6 (HIGH).

How severe is CVE-2000-0323?

This vulnerability has a CVSS 2.0 base score of 7.6, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2000-0323?

Check the references section for vendor advisories and patches from microsoft. Update jet to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2000-0323?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2000-0323 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2000

View all