LiveActive security incident?Get immediate response
CVE Record

CVE-1999-0969: The Windows NT RPC service allows remote attackers to conduct a denial of service using spoofed malformed R...

The Windows NT RPC service allows remote attackers to conduct a denial of service using spoofed malformed RPC packets which generate an error message that is sent to the spoofed host, potentially setting up a loop, aka Snork.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

A late-1990s flaw in the Windows NT Remote Procedure Call service, known as "Snork," lets an attacker send forged RPC packets that cause two NT servers to bounce error messages back and forth. The resulting loop can consume CPU and network bandwidth, degrading or disabling affected systems. It is a denial-of-service issue, not a data breach, and applies to legacy Windows NT environments. Exposure is limited to legacy Windows NT 4.0 (and prior) hosts still running the RPC service on UDP ports reachable from untrusted networks. Modern Windows Server and desktop editions are not in scope. Any surviving NT systems in industrial, lab, or archival environments without the MS98-014 patch remain theoretically vulnerable, though such systems are rare in supported production estates today. Low priority for modern estates. Only relevant if the business still operates unsupported Windows NT systems; in that case treat as part of a legacy-decommissioning workstream rather than an emergency patch cycle. No customer data exposure risk is indicated by the sources. Mitigation focus: Apply the Microsoft fix referenced in MS98-014 / KB Q193233 on any surviving Windows NT hosts.; Block or filter inbound UDP traffic to RPC endpoint mapper ports (notably UDP 135) at the network perimeter.; Retire remaining Windows NT systems and migrate services to a supported Windows Server release..

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-1999-0969 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.