# CVE-2013-20004: Denial of service in n/a

> An attacker can cause a denial of service in StarWind iSCSI target by exhausting memory through repeated connections to non-existent targets.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Feb 2022
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-rrqv-qhmg-w4f2

## What is CVE-2013-20004?

CVE-2013-20004 is a critical denial of service vulnerability in n/a, published on 6 Feb 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A flaw was found in StarWind iSCSI target. StarWind service does not limit client connections and allocates memory on each connection attempt. An attacker could create a denial of service state by trying to connect a non-existent target multiple times. This affects iSCSI SAN (Windows Native) Version 6.0, build 2013-01-16.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

## Which versions are affected by CVE-2013-20004?

It affects 1 product.


Products: Starwindsoftware Iscsi San.

## How do I fix CVE-2013-20004?

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

## Is CVE-2013-20004 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-20001](https://insights.sbomify.com/CVE-2007-20001/): Denial of service in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-20004 and fix it if it is affected.

What it is: CVE-2013-20004 is a critical denial of service vulnerability in n/a, published on 6 Feb 2022. 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-2013-20004 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-2013-20004/ (Markdown: https://insights.sbomify.com/CVE-2013-20004/index.md)
```

## Sources

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

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