CVE-2000-1218: Critical severity Microsoft Windows 2000 vulnerability

Published Apr 14, 2000
·
Updated

The default configuration for the domain name resolver for Microsoft Windows 98, NT 4.0, 2000, and XP sets the QueryIpMatching parameter to 0, which causes Windows to accept DNS updates from hosts that it did not query, which allows remote attackers to poison the DNS cache.

Affected Software

34 affected components
Microsoft Windows 2000
Microsoft Windows 2000=sp1
Microsoft Windows 2000=sp2
Microsoft Windows 2000=sp3
Microsoft Windows 2000=sp4
Microsoft Windows 98=gold
Microsoft Windows 98SE
Microsoft Windows NT=4.0
Microsoft Windows NT=4.0
Microsoft Windows NT=4.0-sp1
Microsoft Windows NT=4.0-sp1
Microsoft Windows NT=4.0-sp2
Microsoft Windows NT=4.0-sp2
Microsoft Windows NT=4.0-sp3
Microsoft Windows NT=4.0-sp3
Microsoft Windows NT=4.0-sp4
Microsoft Windows NT=4.0-sp4
Microsoft Windows NT=4.0-sp5
Microsoft Windows NT=4.0-sp5
Microsoft Windows NT=4.0-sp6
Microsoft Windows NT=4.0-sp6
Microsoft Windows NT=4.0-sp6a
Microsoft Windows NT=4.0-sp6a
Microsoft Windows XP
Microsoft Windows XP
Microsoft Windows XP=gold
Microsoft Windows XP=sp1
Microsoft Windows XP=sp1
Microsoft Windows XP=sp2
Microsoft Windows XP=sp2
Microsoft Windows 2000
Microsoft Windows 98
Microsoft Windows 98SE
Microsoft Windows XP

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Configuration

    Change the QueryIpMatching setting from 0 to a non-zero value (enable IP matching) so the resolver only accepts DNS updates from the host it queried, preventing acceptance of unsolicited DNS updates.

    Microsoft Windows domain name resolver QueryIpMatching = non-zero (enable IP matching)

Event History

Apr 14, 2000
CVE Published
04:00 AM
Data Sourced
via NVD·04:00 AM
DescriptionSeverityWeaknessAffected Software
Apr 21, 2005
CVE Published
via MITRE·04:00 AM
Data Sourced
via MITRE·04:00 AM
Description

Frequently Asked Questions

1

What is the severity of CVE-2000-1218?

CVE-2000-1218 is considered critical because it allows remote attackers to poison the DNS cache.

2

How do I fix CVE-2000-1218?

To fix CVE-2000-1218, configure the QueryIpMatching parameter to a value other than 0.

3

What systems are affected by CVE-2000-1218?

CVE-2000-1218 affects Microsoft Windows 98, NT 4.0, 2000, and XP, especially in their default configurations.

4

Can CVE-2000-1218 be exploited remotely?

Yes, CVE-2000-1218 can be exploited remotely by attackers sending malicious DNS updates.

5

What are the potential impacts of CVE-2000-1218?

The potential impacts of CVE-2000-1218 include unauthorized access to sensitive information and the ability to redirect network traffic.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203