LiveActive security incident?Get immediate response
CVE Record

CVE-2000-0673: The NetBIOS Name Server (NBNS) protocol does not perform authentication, which allows remote attackers to c...

The NetBIOS Name Server (NBNS) protocol does not perform authentication, which allows remote attackers to cause a denial of service by sending a spoofed Name Conflict or Name Release datagram, aka the "NetBIOS Name Server Protocol Spoofing" vulnerability.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

A design flaw in the legacy NetBIOS Name Server (NBNS) protocol lets an unauthenticated attacker on the network trick Windows systems into dropping their computer names. A spoofed Name Conflict or Name Release message can knock hosts off the network, causing outages for file sharing, printing, and login services that rely on NetBIOS. The issue is old (2000) and primarily affects legacy Windows environments. Exposure is limited to environments still running NetBIOS over TCP/IP (UDP 137) where legacy Windows hosts are reachable, or where NetBIOS traffic traverses untrusted segments. Modern networks that disable NetBIOS or block UDP 137 at the perimeter and between segments are largely insulated. Legacy OT, industrial, or unpatched Windows NT/2000/XP-era systems remain the realistic exposure surface. Low priority for modern estates that have retired NetBIOS; moderate priority where legacy Windows or OT systems still rely on NBNS. Treat as a hygiene item within a legacy-protocol reduction program rather than an emergency patch. Mitigation focus: Apply Microsoft security update MS00-047 on any remaining affected Windows NT/2000-era hosts.; Disable NetBIOS over TCP/IP where not required and prefer SMB direct hosting on modern Windows.; Block UDP/137 and TCP/139 at network perimeters and between untrusted segments..

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-0673 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
3Source 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.