LiveActive security incident?Get immediate response
CVE Record

CVE-2000-0487: The Protected Store in Windows 2000 does not properly select the strongest encryption when available, which...

The Protected Store in Windows 2000 does not properly select the strongest encryption when available, which causes it to use a default of 40-bit encryption instead of 56-bit DES encryption, aka the "Protected Store Key Length" vulnerability.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

Windows 2000's Protected Store, which safeguards sensitive material like private keys and passwords, defaulted to weaker 40-bit encryption even when stronger 56-bit DES was available. That means data assumed to be secured at a higher strength was actually protected by an easier-to-break key, undermining trust in the system's cryptographic guarantees on affected machines. Exposure is limited to legacy Windows 2000 systems still in operation. Modern Windows releases are unaffected. Any residual risk applies to isolated legacy environments (industrial, embedded, or archived VMs) where secrets stored via the Protected Store on Win2000 may have weaker-than-expected confidentiality. Low priority for any modern estate. Only relevant if legacy Windows 2000 systems still hold sensitive data. Address as part of routine legacy decommissioning rather than emergency response; there is no evidence of active exploitation and Microsoft published a fix in 2000. Mitigation focus: Apply the Microsoft MS00-032 patch on any surviving Windows 2000 hosts.; Retire or isolate remaining Windows 2000 systems, which are long past end of support.; Rotate any secrets historically stored in the Protected Store on affected legacy hosts..

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-0487 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.