CVE-1999-0228: Microsoft Windows NT denial of service in RPC Locator

CVE-1999-0228 · Severity: medium · CVSS 5 · Published 1997-02-07

A vulnerability in the Windows NT Remote Procedure Call (RPC) Locator service allows an attacker to disrupt system operations. The RPC Locator is a background service that helps different software components communicate across a network. An exploit could cause this service to crash or hang, potentially leading to a denial of service that prevents legitimate users or applications from accessing network resources.

Technologies: Microsoft Windows Nt. Vendors: Microsoft.

Quick answers

Is CVE-1999-0228 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-1999-0228 being exploited in the wild.
How severe is CVE-1999-0228?
Medium severity, with a CVSS score of 5, published 7 February 1997.
Which products and versions are affected?
Microsoft Windows NT.
Is there a fix for CVE-1999-0228?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-1999-0228 attacked?
It is attacked over the network, in an operating system.
Am I affected by CVE-1999-0228?
Check whether you run Microsoft Windows Nt. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A denial of service vulnerability exists in the RPCSS.EXE program, which functions as the RPC Locator service in Microsoft Windows NT. The vulnerability allows a remote, unauthenticated attacker to send malicious requests to the RPC service, causing it to fail or become unresponsive. This disrupts the ability of the operating system to resolve RPC service locations, impacting distributed applications and system management tools. The issue is reachable over the network without user interaction. Microsoft addressed this issue in legacy knowledge base article Q162567.

Affected products

  • Microsoft Windows NT

Timeline

  • 1997-02-07: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.