CVE-2003-0117
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 the HTTP receiver function (BizTalkHTTPReceive.dll ISAPI) of Microsoft BizTalk Server 2002 allows attackers to execute arbitrary code via a certain request to the HTTP receiver.
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 confidenceBuffer overflow vulnerability in the HTTP receiver ISAPI extension (BizTalkHTTPReceive.dll) of Microsoft BizTalk Server 2002 allows remote attackers to execute arbitrary code via crafted HTTP requests to the HTTP receiver function.
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= 2002CVSS 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.
-
Identify installed BizTalk Server versionCheck the installed BizTalk Server version via Windows Add/Remove Programs, or check the BizTalk Server Administration documentation, or look at the BizTalk Server installation directory for version information.Affected if The installed version is Microsoft BizTalk Server 2002 exactly (version 6.0 or 6.1 in some listings)
-
Locate BizTalkHTTPReceive.dllSearch for BizTalkHTTPReceive.dll on the system - typically found in the BizTalk Server installation path or in the IIS scripts/bin directory used for ISAPI extensions.Affected if The file BizTalkHTTPReceive.dll exists on the server in an ISAPI extensions directory
-
Verify HTTP receiver ISAPI extension is registered in IISOpen IIS Manager, expand the server node, click on 'ISAPI and CGI Restrictions' or check the Web Service Extension configuration to see if BizTalk HTTP Receive is listed as an allowed extension.Affected if The BizTalk HTTP Receive ISAPI extension is registered and allowed in IIS
-
Confirm HTTP receiver endpoint is configured and accessibleCheck BizTalk Server configuration for HTTP receiver ports, or test access to the configured HTTP receive URL (typically with a path like /BTSHTTPReceive.dll or similar).Affected if An HTTP receive location is enabled and configured to accept HTTP requests on any port or path
A system is affected if BizTalk Server 2002 is installed with the BizTalkHTTPReceive.dll ISAPI extension enabled and an active HTTP receiver endpoint configured to accept HTTP traffic.
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 patch for CVE-2003-0117 if available; otherwise, disable the BizTalk HTTP receiver ISAPI extension or filter HTTP traffic to the affected endpoint until patching or upgrade to a supported BizTalk Server version can be completed.
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2003-0117 — 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-0117 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