# CVE-2002-0123: Memory corruption in n/a

> Remote attackers can cause denial of service or execute arbitrary commands via a long HTTP request in 4D WS4D/eCommerce web server.

- **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 Apr 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-789r-hxfx-3jmr

## What is CVE-2002-0123?

CVE-2002-0123 is a high-severity memory corruption vulnerability in n/a, published on 2 Apr 2003. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

MDG Computer Services Web Server 4D WS4D/eCommerce 3.0 and earlier, and possibly 3.5.3, allows remote attackers to cause a denial of service and possibly execute arbitrary commands via a long HTTP request.

## Which versions are affected by CVE-2002-0123?

It affects 1 product.


Products: Mdg Computer Services Web Server 4d Ecommerce.

## How do I fix CVE-2002-0123?

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

## Is CVE-2002-0123 being exploited?

There is no known exploitation of CVE-2002-0123 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2002-0124](https://insights.sbomify.com/CVE-2002-0124/): Path traversal in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-0123 and fix it if it is affected.

What it is: CVE-2002-0123 is a high-severity memory corruption vulnerability in n/a, published on 2 Apr 2003. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2002-0123 in the wild and no public exploit code.

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-2002-0123/ (Markdown: https://insights.sbomify.com/CVE-2002-0123/index.md)
```

## Sources

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

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