# CVE-2002-1780: Denial of service in n/a

> Remote attackers can crash BPM Studio Pro's webserver by requesting MS-DOS devices, though the root cause is disputed as a Windows bug.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/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:** 21 Jun 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-fq5j-97fp-p9jc

## What is CVE-2002-1780?

CVE-2002-1780 is a medium-severity denial of service vulnerability in n/a, published on 21 Jun 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

BPM Studio Pro 4.2 by ALCATech GmbH includes a webserver that allows a remote attacker to cause a denial of service (crash) by sending a URL request for a MS-DOS device such as con.  NOTE: it has been disputed that this and possibly other application-level DOS device issues stem from a bug in Windows, and as such, such applications should not be considered vulnerable themselves.

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

It affects 1 product.


Products: Alcatech Gmbh Bpm Studio Pro.

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

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

## Is CVE-2002-1780 being exploited?

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

## Other vulnerabilities in n/a

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

## Fix prompt for AI coding agents

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

What it is: CVE-2002-1780 is a medium-severity denial of service vulnerability in n/a, published on 21 Jun 2005. 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-1780 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-1780/ (Markdown: https://insights.sbomify.com/CVE-2002-1780/index.md)
```

## Sources

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

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