CVE-2008-0080
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 · uneditedHeap-based buffer overflow in the WebDAV Mini-Redirector in Microsoft Windows XP SP2, Server 2003 SP1 and SP2, and Vista allows remote attackers to execute arbitrary code via a crafted WebDAV response.
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 confidenceHeap-based buffer overflow in the Windows WebDAV Mini-Redirector allows remote attackers to execute arbitrary code via a crafted WebDAV response, affecting Windows XP SP2, Server 2003 SP1/SP2, and Vista.
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 dataall versionsCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Windows versionRun 'winver' or check system properties to confirm the Windows version. Look for Windows XP SP2, Server 2003 SP1/SP2, or Vista.Affected if The system is running Windows XP SP2, Server 2003 SP1/SP2, or Vista.
-
Check if WebDAV Mini-Redirector driver is loadedOpen Command Prompt and run 'sc query mrxdav' to query the status of the WebDAV Mini-Redirector service driver (mrxdav.sys).Affected if The mrxdav driver service exists and is running on the system.
-
Verify WebDAV client component presenceCheck for the presence of mrxdav.sys in the system directory (typically C:\Windows\System32\drivers\mrxdav.sys) using 'dir C:\Windows\System32\drivers\mrxdav.sys'.Affected if The mrxdav.sys file exists on the system.
-
Check WebDAV redirector configurationRun 'reg query HKLM\SYSTEM\CurrentControlSet\Services\Mrxdav' to query the WebDAV Mini-Redirector registry configuration.Affected if The WebDAV Mini-Redirector registry key exists (indicating the component is installed).
The system is affected if it runs Windows XP SP2, Server 2003 SP1/SP2, or Vista AND has the WebDAV Mini-Redirector (mrxdav.sys) installed and enabled, since the buffer overflow vulnerability exists in all versions of this component.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataApply Microsoft security patches for CVE-2008-0080; until patched, restrict WebDAV connectivity to trusted sources and disable the WebDAV Mini-Redirector if not required.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2008-0080 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2008-0080 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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