CVE-1999-0499: Microsoft Windows NT information disclosure via SNMP registry keys

CVE-1999-0499 · Severity: high · CVSS 7.5 · Published 1997-01-01

A security issue in older Microsoft Windows NT systems allows sensitive network share information to be exposed through the SNMP service. This could allow an unauthorized person to see details about private file shares and network configurations, potentially leading to unauthorized access to company data. This vulnerability affects the way the system manages network identity and resource sharing.

Technologies: Microsoft Windows 2000, Microsoft Windows Nt. Vendors: Microsoft.

Quick answers

Is CVE-1999-0499 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-1999-0499 being exploited in the wild.
How severe is CVE-1999-0499?
High severity, with a CVSS score of 7.5, published 1 January 1997.
Which products and versions are affected?
Microsoft Windows NT.
Is there a fix for CVE-1999-0499?
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-0499 attacked?
It is attacked over the network, in an operating system.
Am I affected by CVE-1999-0499?
Check whether you run Microsoft Windows 2000 or 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

The vulnerability exists in Microsoft Windows NT where NETBIOS share information is inadvertently exposed via SNMP registry keys. An unauthenticated remote attacker can query the SNMP service to enumerate network shares and other system configuration details stored in the registry. This is primarily an information disclosure vulnerability that facilitates further attacks by revealing the internal network structure and available resources. The issue stems from improper access controls or default configurations within the SNMP agent's mapping of registry data.

Affected products

  • Microsoft Windows NT

Timeline

  • 1997-01-01: disclosed: Initial publication date in NVD.

References

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