dbcve.org
Windows 2000Operating system · Microsoft

CVE-2007-2218

HIGH · 9.3 CVSS v2.0 Published 2007-06-12
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
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
Unspecified vulnerability in the Windows Schannel Security Package for Microsoft Windows 2000 SP4, XP SP2, and Server 2003 SP1 and SP2, allows remote servers to execute arbitrary code or cause a denial of service via crafted digital signatures that are processed during an SSL handshake.

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

Vulnerability in Windows Schannel Security Package allows remote attackers to execute arbitrary code or cause denial of service by sending specially crafted digital signatures during SSL/TLS handshake processing. The flaw affects how Windows validates digital signatures from remote servers during the initial SSL connection establishment.

MitigationApply Microsoft security updates for affected Windows versions (2000 SP4, XP SP2, Server 2003 SP1/SP2). For systems no longer supported by Microsoft, consider network isolation or upgrading to supported Windows 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
Windows XpOperating system
Affected:all versions

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
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/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. Identify Windows version and Service Pack
    Run 'winver' or check system properties, or run 'systeminfo' from command prompt to get exact OS version and Service Pack level
    Affected if Version is Windows 2000 (any SP), Windows XP (any SP), or Windows Server 2003 SP1 or SP2
  2. Confirm Schannel is in use
    Schannel is the Windows SSPI provider for SSL/TLS. Check that the system uses SSL/TLS by examining if IIS, SQL Server, Remote Desktop, or other SSL-enabled services are configured, or run 'netsh http show sslcert' to list SSL bindings
    Affected if System has any SSL/TLS enabled services or applications that establish SSL/TLS connections using Windows Schannel
  3. Verify SSL/TLS handshake capability
    Attempt an outbound SSL connection from the system (e.g., browse to an HTTPS site) or check for accepted inbound SSL connections. On Server systems, check IIS for enabled HTTPS bindings via IIS Manager or 'appcmd list site'
    Affected if The system can initiate or accept SSL/TLS connections - this is required for the vulnerable code path to be exercised during handshake signature validation

The system is affected if it runs any version of Windows 2000, Windows XP, or Windows Server 2003 SP1/SP2 AND actively uses SSL/TLS connections through the Schannel security package.

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 security updates for affected Windows versions (2000 SP4, XP SP2, Server 2003 SP1/SP2). For systems no longer supported by Microsoft, consider network isolation or upgrading to supported Windows versions.

Recommended fix High confidence

For end-of-life systems (Windows 2000, XP), migrate to a supported Windows version such as Windows 10 or 11, or Windows Server 2016/2019/2022

  1. Open Windows Update or visit https://update.microsoft.com
  2. Check for and install the Microsoft security update for CVE-2007-2218 (security bulletin MS07-031)
  3. If automatic updates are enabled, ensure the update is downloaded and installed
  4. Restart the system after applying the update
  5. Verify the update was installed by checking Windows Update history for security update KB935966
Caveat Windows 2000 and Windows XP reached end of support; legacy applications may not function on newer Windows versions; verify application compatibility before migration

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

Fix this in Windows 2000 Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2007-2218 — 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-2218 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