# What is CVE-2003-0231?

> CVE-2003-0231 is a medium-severity flaw (CVSS 5.0) in SQL Server from Microsoft, published on 27 August 2003. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 36%. If you run an affected version, plan in the vendor’s fix.

Canonical page: https://www.precursorintelligence.com/what-is/cve-2003-0231

## At a glance

- **Verdict:** Fix this soon. Not confirmed as exploited yet, but serious or likely enough that it should not wait for a quiet month.
- **Precursor Intelligence risk score:** 34 out of 100 (Low); action: Monitor. Kept up to date as the evidence changes.
- **Severity:** Medium (CVSS 5.0 out of 10)
- **Known to be exploited:** No, not on the list of flaws known to be exploited today
- **Chance of use in the next 30 days:** 36% (latest exploit-likelihood forecast)
- **Published:** 27 August 2003
- **Record last updated:** 16 June 2026
- **Main product:** SQL Server from Microsoft
- **Affected products:** 2

## What is CVE-2003-0231? In plain terms

It can be attacked from anywhere on the internet without logging in. If it works, the attacker can slow it down.

### The official description

Microsoft SQL Server 7, 2000, and MSDE allows local or remote authenticated users to cause a denial of service (crash or hang) via a long request to a named pipe.

### What kind of flaw is it?

- Unknown: Unknown

### How an attack on it works

- Where an attacker can be: Anywhere on the internet
- How hard it is to pull off: Easy: no special conditions
- Login needed first: No login needed
- What an attacker gets: Can slow it down

Severity vector: `AV:N/AC:L/Au:N/C:N/I:N/A:P`

## Is CVE-2003-0231 being exploited? Not that we know of

It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 36%. That can change at any time, which is why we keep watching.

Exploit likelihood over the last 7 days: 36%, 36%, 36%, 36%, 36%, 36%, 36%.

### Timeline

- 27 August 2003: Published
- 7 March 2023: Exploit likelihood fell
- 9 August 2023: Exploit likelihood jumped
- 16 June 2026: Record last updated

### How Precursor Intelligence ranks it

CVE-2003-0231 scores **34 out of 100 (Low)**, with the action "Monitor".

Every published flaw gets a risk score from 0 to 100, kept up to date as the evidence changes. Four things go into the score, from the one that counts most to the ones that count less:

- Evidence it is being exploited: biggest factor
- How severe it is: strong factor
- How widely exposed it is: smaller factor
- Threat activity around it: smaller factor

85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score. When this flaw matches software you track, it lands in your list with its score and the reasons behind it.

## Who is affected by CVE-2003-0231?

The published record lists 2 products.

- [SQL Server](https://www.precursorintelligence.com/product/microsoft/sql_server) by [Microsoft](https://www.precursorintelligence.com/vendors/microsoft) (Application): 7.0, 7.0-sp1, 7.0-sp2, 7.0-sp3, 7.0-sp4, 2000, 2000-sp1, 2000-sp2, 2000-sp3a, 2000-sp3
- [Data Engine](https://www.precursorintelligence.com/product/microsoft/data_engine) by [Microsoft](https://www.precursorintelligence.com/vendors/microsoft) (Application): 1.0

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

1. **Check whether you run it.** Compare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list.
2. **Apply the vendor’s fix.** Install the latest update from the vendor. The references list where the vendor has published details.
3. **If you can’t patch today.** Follow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
4. **Keep an eye on it.** Track the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood.

### References

- [atstake.com](http://www.atstake.com/research/advisories/2003/a072303-2.txt)
- [kb.cert.org](http://www.kb.cert.org/vuls/id/918652) (Government resource)
- [docs.microsoft.com](https://docs.microsoft.com/en-us/security-updates/securitybulletins/2003/ms03-031)
- [oval.cisecurity.org](https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A299)

## Questions

### What is CVE-2003-0231?

CVE-2003-0231 is a medium-severity flaw in SQL Server from Microsoft, published on 27 August 2003. It can be attacked from anywhere on the internet without logging in. If it works, the attacker can slow it down.

### How serious is CVE-2003-0231?

It scores 5.0 out of 10 on the CVSS severity scale, which is medium. Our risk score for CVE-2003-0231 is 34 out of 100, which is Low. Its action is "Monitor". Not confirmed as exploited yet, but serious or likely enough that it should not wait for a quiet month.

### Is CVE-2003-0231 being exploited?

It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 36%. That can change at any time, which is why we keep watching.

### Which versions does CVE-2003-0231 affect?

For SQL Server from Microsoft: 7.0, 7.0-sp1, 7.0-sp2, 7.0-sp3, 7.0-sp4, 2000 and 4 more. The record lists 2 products in all, each with its versions, under "Who is affected" on this page.

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

Install the update the vendor names in its advisory. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet.

## Does CVE-2003-0231 affect you?

Precursor Intelligence keeps checking for you:

- **Tell us what you run.** Pick your software from a list, or let us work it out from your website.
- **We match it to every flaw.** Over 400,000 published flaws, checked against your list.
- **Ranked by real-world risk.** Every flaw gets a 0 to 100 risk score, kept up to date, led by evidence criminals are using it.
- **Told as soon as we know.** An alert by email, in the app or by webhook to your own tools.

Start free (no card, nothing to install): https://www.precursorintelligence.com/register
Book a demo: https://www.precursorintelligence.com/contact