CVE-2003-0353
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 · uneditedBuffer overflow in a component of SQL-DMO for Microsoft Data Access Components (MDAC) 2.5 through 2.7 allows remote attackers to execute arbitrary code via a long response to a broadcast request to UDP port 1434.
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 · moderate confidenceBuffer overflow vulnerability in the SQL-DMO component of Microsoft Data Access Components (MDAC) versions 2.5 through 2.7 allows remote attackers to execute arbitrary code by sending a specially crafted long response to a broadcast request on UDP port 1434.
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= 1.5= 2.0= 2.1= 2.1.1.3711.11= 2.5= 2.6= 2.7= 2.12.4202.3CVSS 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
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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.
-
Check if SQL Server Browser service is runningOpen Services console (services.msc) and look for 'SQL Server Browser' service, or run 'netstat -an | findstr "1434"' to check if UDP port 1434 is listeningAffected if The SQL Server Browser service is running and listening on UDP port 1434, or netstat shows UDP 0.0.0.0:1434 in LISTENING state
-
Determine installed MDAC version via registryOpen Registry Editor and navigate to HKLM\Software\Microsoft\DataAccess, or run 'reg query "HKLM\Software\Microsoft\DataAccess" /v Version'Affected if The Version value in the registry matches any of these: 1.5, 2.0, 2.1, 2.1.1.3711.11, 2.5, 2.6, 2.7, 2.12.4202.3
-
Check MDAC version via file propertiesLocate mdac_typ.dll in the Windows\System32 folder (or WinNT\System32 for older Windows), right-click and view Properties > Version tab, or run 'dir %SystemRoot%\System32\mdac_typ.dll' to find the file and check its versionAffected if The mdac_typ.dll file version matches 1.5.x, 2.0.x, 2.1.x, 2.5.x, 2.6.x, 2.7.x, or 2.12.x and falls within the affected range
-
Verify SQL-DMO component presenceCheck for presence of SQLDMO.dll (SQL Distributed Management Objects) in the system, typically found in Windows\System32 or through SQL Server installation directories, or check registry under HKLM\Software\Microsoft\Microsoft SQL Server\Setup for SQL-DMO componentsAffected if SQLDMO.dll is installed and registered on the system, particularly on machines with SQL Server 2000 or MSDE installations
A system is affected if it is running any MDAC version between 1.5 and 2.7 (inclusive) with the SQL Server Browser service enabled and listening on UDP port 1434, exposing the SQL-DMO component to the vulnerability.
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 dataBlock UDP port 1434 at network perimeter firewalls, and apply Microsoft's security patches for MDAC to remediate the vulnerability.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2003-0353 — 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-2003-0353 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