How severe is CVE-2000-0199?

CVE-2000-0199 has a CVSS 2.0 base score of 7.2, rated high severity.

Is CVE-2000-0199 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (70th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2000-0199?

CVE-2000-0199 affects Microsoft Sql Server. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2000-0199?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2000-0199 published?

CVE-2000-0199 was published on 2000-03-14 and last updated on 2026-06-16.

CVE-2000-0199

CVE-2000-0199 is a high-severity vulnerability in Microsoft Sql Server with a CVSS 2.0 base score of 7.2. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: High (CVSS 2.0 base score 7.2)
EPSS exploit prediction: 1% (70th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Microsoft Sql Server
Published: 2000-03-14
Last modified: 2026-06-16

Description

When a new SQL Server is registered in Enterprise Manager for Microsoft SQL Server 7.0 and the "Always prompt for login name and password" option is not set, then the Enterprise Manager uses weak encryption to store the login ID and password.

Frequently asked questions

What is CVE-2000-0199?: When a new SQL Server is registered in Enterprise Manager for Microsoft SQL Server 7.0 and the "Always prompt for login name and password" option is not set, then the Enterprise Manager uses weak encryption to store the login ID and password.
How severe is CVE-2000-0199?: CVE-2000-0199 has a CVSS 2.0 base score of 7.2, rated high severity.
Is CVE-2000-0199 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (70th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2000-0199?: CVE-2000-0199 affects Microsoft Sql Server. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2000-0199?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2000-0199 published?: CVE-2000-0199 was published on 2000-03-14 and last updated on 2026-06-16.

References

http://www.securityfocus.com/bid/1055

Affected products (1)

cpe:2.3:a:microsoft:sql_server:7.0:*:*:*:*:*:*:*

More vulnerabilities in Microsoft Sql Server

CVE-2002-1145 — Critical (CVSS 10.0): The xp_runwebtask stored procedure in the Web Tasks component of Microsoft SQL Server 7.0 and 2000, Microsoft Data…
CVE-2002-0721 — Critical (CVSS 10.0): Microsoft SQL Server 7.0 and 2000 installs with weak permissions for extended stored procedures that are associated…
CVE-2018-8273 — Critical (CVSS 9.8): A buffer overflow vulnerability exists in the Microsoft SQL Server that could allow remote code execution on an…
CVE-2009-3126 — Critical (CVSS 9.3): Integer overflow in GDI+ in Microsoft Internet Explorer 6 SP1, Windows XP SP2 and SP3, Office XP SP3, Office 2003 SP3,…
CVE-2009-2528 — Critical (CVSS 9.3): GDI+ in Microsoft Office XP SP3 does not properly handle malformed objects in Office Art Property Tables, which allows…
CVE-2009-2504 — Critical (CVSS 9.3): Multiple integer overflows in unspecified APIs in GDI+ in Microsoft .NET Framework 1.1 SP1, .NET Framework 2.0 SP1 and…

All CVEs affecting Microsoft Sql Server →