LiveActive security incident?Get immediate response
CVE Record

CVE-2000-1087: The xp_proxiedmetadata function in Microsoft SQL Server 2000 and SQL Server Desktop Engine (MSDE) does not...

The xp_proxiedmetadata function in Microsoft SQL Server 2000 and SQL Server Desktop Engine (MSDE) does not properly restrict the length of a buffer before calling the srv_paraminfo function in the SQL Server API for Extended Stored Procedures (XP), which allows an attacker to cause a denial of service or execute arbitrary commands, aka the "Extended Stored Procedure Parameter Parsing" vulnerability.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

An older Microsoft SQL Server 2000 and MSDE component contained a flaw in the xp_proxiedmetadata extended stored procedure that could let an attacker crash the database or run unauthorized commands on the server. Microsoft issued a fix in bulletin MS00-092. Any organization still running these legacy database engines faces meaningful business risk and should confirm the patch is applied or the platform is retired. Exposure is limited to systems still running unpatched SQL Server 2000 or MSDE where an attacker can reach the database and invoke extended stored procedures. In most modern estates these engines are end-of-life, but MSDE frequently shipped embedded in third-party applications and may persist in legacy servers, appliances, or manufacturing environments. Priority is elevated where any SQL Server 2000 or MSDE remains in production. Because both platforms are end-of-life, the durable action is decommissioning or migration; short-term, confirm MS00-092 is applied and reduce network exposure. If no legacy SQL Server 2000/MSDE exists, priority drops to housekeeping. Mitigation focus: Apply Microsoft security bulletin MS00-092 to any surviving SQL Server 2000 or MSDE instance.; Retire or upgrade SQL Server 2000 and MSDE, which are past end of support.; Restrict network access to SQL Server ports so only trusted application hosts can reach the database..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2000-1087 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.