Security readout for executives and security teams
Plain-English summary
This is a legacy Windows 2000 Telnet service flaw. A person who already has local access could abuse predictable named pipe handling to run arbitrary commands. The source bundle does not show active exploitation or a modern severity score.
Executive priority
Treat this as a legacy-system risk. It is unlikely to affect modern Windows estates, but any remaining Windows 2000 Telnet deployment should be isolated, patched, or retired because local compromise could become broader system control.
Technical view
Microsoft Windows 2000 Telnet service creates named pipes with predictable names and does not properly verify them. A local user may precreate the expected pipe and associate it with a malicious program, leading to arbitrary command execution.
Likely exposure
Exposure appears limited to Microsoft Windows 2000 systems using the Telnet service. The structured affected-product data is incomplete, so confirm against Microsoft MS01-031 and internal legacy asset records.
Exploitation context
The CVE describes local abuse, not remote unauthenticated exploitation. KEV is false, and the provided sources do not state active exploitation. Evidence is limited to the CVE description, Microsoft bulletin reference, and X-Force entry.
Researcher notes
The record is sparse: no CVSS, CWE, CPE, or detailed affected-version range is provided. The vulnerability is the second named-pipe variant referenced for Windows 2000 Telnet service; use MS01-031 as the primary remediation authority.
Mitigation direction
- Review Microsoft MS01-031 and apply the vendor-provided update where applicable.
- Disable the Windows 2000 Telnet service if it is not required.
- Restrict local and Telnet access to trusted administrators only.
- Prioritize retirement or isolation of remaining Windows 2000 hosts.
- Monitor legacy hosts for unusual Telnet service or local process activity.
Validation and detection
- Inventory Windows 2000 assets and identify systems running Telnet service.
- Confirm whether MS01-031 remediation is installed or otherwise addressed.
- Verify Telnet is disabled where no business requirement exists.
- Review local user access on any remaining affected systems.
- Check security monitoring for suspicious local command execution on legacy hosts.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-2001-0350 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- MS01-031CVE reference · vendor-advisory, x_refsource_MS
- win2k-telnet-pipe-privileges(6664)CVE reference · vdb-entry, x_refsource_XF
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.