dbcve.org
Windows 2000Operating system · Microsoft

CVE-2007-1205

HIGH · 9.3 CVSS v2.0 Published 2007-04-10
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 Microsoft Agent (msagent\agentsvr.exe) in Windows 2000 SP4, XP SP2, and Server 2003, 2003 SP1, and 2003 SP2 allows remote attackers to execute arbitrary code via crafted URLs, which result in memory corruption.

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

Memory corruption vulnerability in Microsoft Agent (msagent\agentsvr.exe) allows remote code execution via crafted URLs on Windows 2000 SP4, XP SP2, and Server 2003/2003 SP1/SP2.

MitigationApply Microsoft security patches for this vulnerability; if patches unavailable, consider disabling or blocking Microsoft Agent service and restricting URL handling where possible.

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:= gold= 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. Check Windows version
    Open System Properties (winver or sysdm.cpl) or run 'ver' command in cmd.exe. Identify if the OS is Windows 2000 (any SP), Windows XP (any SP), or Windows Server 2003 (gold, SP1, or SP2).
    Affected if The installed OS is Windows 2000, Windows XP, or Windows Server 2003 (gold/SP1/SP2)
  2. Verify Microsoft Agent component exists
    Navigate to %windir%\msagent\ or check for the presence of agentsvr.exe file in the Windows system directory. Run 'dir %windir%\msagent\agentsvr.exe' in command prompt.
    Affected if The file msagent\agentsvr.exe exists on the system
  3. Check Microsoft Agent service status
    Open Services (services.msc) and look for 'Microsoft Agent' service, or run 'sc query msagent' in command prompt to check if the service is present and its state.
    Affected if The Microsoft Agent service is installed and running on the system
  4. Confirm agentsvr.exe version
    Right-click on %windir%\msagent\agentsvr.exe, select Properties, go to Version tab, and note the File Version. Compare this version against known vulnerable versions for this CVE.
    Affected if The agentsvr.exe version matches the vulnerable version range for CVE-2007-1205 (if known) or the file is present on an affected OS version
  5. Check for URL handling capability
    Verify that Microsoft Agent is configured to handle URL requests. Check registry key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\agentsvr.exe or examine if the 'Microsoft Agent' component handles web-based agent requests.
    Affected if Microsoft Agent is configured to handle HTTP/URL requests and the affected msagent\agentsvr.exe binary is present

A system is affected if it runs Windows 2000, XP, or Server 2003 (gold/SP1/SP2) AND has the Microsoft Agent component (agentsvr.exe) installed with URL handling enabled.

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 patches for this vulnerability; if patches unavailable, consider disabling or blocking Microsoft Agent service and restricting URL handling where possible.

Recommended fix Moderate confidence

Upgrade to a supported Windows version (Windows Vista, Windows 7, Windows Server 2008 or later) as Windows 2000, XP, and Server 2003 are end-of-life and no longer receive security updates

  1. Apply the Microsoft security update for CVE-2007-1205 (MS07-027) from Windows Update or the Microsoft Download Center
  2. Verify the update was successfully installed by checking for security update 932853 in Add or Remove Programs (for XP) or Programs and Features (for Vista/2008+)
  3. If automatic updates are enabled, ensure they are running and patches are being applied
  4. For Windows 2000/XP/Server 2003 systems, confirm the msagent\agentsvr.exe version reflects the patched build
Caveat Windows 2000, XP, and Server 2003 are no longer supported; upgrading may require application compatibility testing and migration planning

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
  • Testing3.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,050
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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