dbcve.org
Windows 2000Operating system · Microsoft

CVE-2007-1748

HIGH · 10.0 CVSS v2.0 Published 2007-04-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
High EPSS Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Stack-based buffer overflow in the RPC interface in the Domain Name System (DNS) Server Service in Microsoft Windows 2000 Server SP 4, Server 2003 SP 1, and Server 2003 SP 2 allows remote attackers to execute arbitrary code via a long zone name containing character constants represented by escape sequences.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A stack-based buffer overflow in the DNS Server Service RPC interface on Windows 2000 Server SP4 and Windows Server 2003 SP1/SP2 allows remote attackers to execute arbitrary code by sending a specially crafted DNS zone name containing character constants represented by escape sequences.

MitigationApply Microsoft's security patches for this vulnerability; for end-of-life systems no longer receiving updates, consider network segmentation, disabling the DNS RPC interface, or upgrading to supported Windows Server versions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Windows 2000Operating system
Affected:all versions
Windows 2003 ServerOperating system
Affected:= sp1= sp2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Windows version
    Run 'winver' or 'systeminfo' from command prompt. Look for Windows 2000 (any version) or Windows Server 2003 with Service Pack 1 or Service Pack 2.
    Affected if System is Windows 2000 any version, or Windows Server 2003 SP1 or SP2.
  2. Verify DNS Server service is installed
    Open Services console (services.msc) or run 'sc query dns' from command prompt. Check if 'DNS Server' service exists and is running.
    Affected if DNS Server service is installed and running on a vulnerable Windows version.
  3. Confirm DNS RPC interface is enabled
    DNS Server RPC interface (DNS.exe listening on RPC ports) is typically enabled by default on Windows Server 2000/2003 when DNS Server role is installed. Check with 'netstat -an | findstr :1025' or review DNS server event logs for RPC activity.
    Affected if DNS Server is accepting RPC connections (port 1025/tcp and others by default for DNS RPC).

System is affected if running Windows 2000 any version or Windows Server 2003 SP1/SP2 with the DNS Server service running and its RPC interface exposed.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Microsoft's security patches for this vulnerability; for end-of-life systems no longer receiving updates, consider network segmentation, disabling the DNS RPC interface, or upgrading to supported Windows Server versions.

Recommended fix High confidence

Replace Windows 2000 Server and Windows Server 2003 with Windows Server 2012 or later (Windows Server 2016/2019/2022 recommended)

  1. 1. Disconnect affected systems from the network immediately to prevent exploitation.
  2. 2. Identify all systems running Windows 2000 Server or Windows Server 2003 SP1/SP2 with DNS Server role enabled.
  3. 3. Replace affected operating systems with a supported version (Windows Server 2008 or later, or Windows Server 2012/2016/2019/2022).
  4. 4. If immediate replacement is not possible, apply Microsoft Security Bulletin MS07-029 (KB935966) as a temporary mitigation.
  5. 5. After patching or upgrading, verify the DNS Server service is functioning correctly.
  6. 6. Reconnect systems to the network only after confirming remediation is complete.
Caveat Both Windows 2000 Server and Windows Server 2003 are end-of-life and no longer receive security updates; migration to supported OS versions is required; application compatibility testing may be needed for DNS-dependent services

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows 2000 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2007-1748 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2007-1748 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data