# CVE-2003-0118: SQL injection in n/a

> Remote attackers can execute operating system commands via SQL injection in Microsoft BizTalk Server's Document Tracking website.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 May 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-83mv-r2r9-9gx9

## What is CVE-2003-0118?

CVE-2003-0118 is a high-severity SQL injection vulnerability in n/a, published on 2 May 2003. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SQL injection vulnerability in the Document Tracking and Administration (DTA) website of Microsoft BizTalk Server 2000 and 2002 allows remote attackers to execute operating system commands via a request to (1) rawdocdata.asp or (2) RawCustomSearchField.asp containing an embedded SQL statement.

## Which versions are affected by CVE-2003-0118?

It affects 1 product.


Products: Microsoft Biztalk Server.

## How do I fix CVE-2003-0118?

No fix has been published for CVE-2003-0118 yet. Limit exposure of the affected software until one is available.

## Is CVE-2003-0118 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2003-0118 exists.

Public exploit code:

- Microsoft BizTalk Server 2000/2002 DTA - 'rawdocdata.asp' SQL Injection (exploitdb)
- Microsoft BizTalk Server 2000/2002 DTA - 'RawCustomSearchField.asp' SQL Injection (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2012-0158](https://insights.sbomify.com/CVE-2012-0158/): Microsoft MSCOMCTL.OCX Remote Code Execution (high 8.8, exploited in the wild)
- [CVE-2009-2496](https://insights.sbomify.com/CVE-2009-2496/): Memory corruption in n/a (critical 9.3)
- [CVE-2007-1201](https://insights.sbomify.com/CVE-2007-1201/): Memory corruption in n/a (critical 9.3)
- [CVE-2007-0940](https://insights.sbomify.com/CVE-2007-0940/): Code injection in n/a (critical 9.3)
- [CVE-2003-0117](https://insights.sbomify.com/CVE-2003-0117/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2003-0118 and fix it if it is affected.

What it is: CVE-2003-0118 is a high-severity SQL injection vulnerability in n/a, published on 2 May 2003. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2003-0118 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2003-0118/ (Markdown: https://insights.sbomify.com/CVE-2003-0118/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2003-0118
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2003-0118
- OSV: https://osv.dev/vulnerability/CVE-2003-0118

---
From sbomify Insights: https://insights.sbomify.com/CVE-2003-0118/
Summaries are generated and may contain mistakes; the official description above is the record.