# CVE-2001-0121: Denial of service in n/a

> Remote attackers can crash ImageCast Control Center or exhaust resources by sending a long string to port 12002.

- **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:** 18 Sep 2001
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-wx94-8j26-vf7x

## What is CVE-2001-0121?

CVE-2001-0121 is a medium-severity denial of service vulnerability in n/a, published on 18 Sep 2001. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ImageCast Control Center 4.1.0 allows remote attackers to cause a denial of service (resource exhaustion or system crash) via a long string to port 12002.

## Which versions are affected by CVE-2001-0121?

It affects 1 product.


Products: Storagesoft Imagecast Ic3.

## How do I fix CVE-2001-0121?

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

## Is CVE-2001-0121 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2001-0121 and fix it if it is affected.

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

## Sources

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

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