# CVE-2020-35579: Denial of service in n/a

> An attacker can cause a denial of service by triggering a request loop through the /sub endpoint's URL parameter handling.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:** 20 Dec 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-cj8c-gw6c-32jv

## What is CVE-2020-35579?

CVE-2020-35579 is a high-severity denial of service vulnerability in n/a, published on 20 Dec 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

tindy2013 subconverter 0.6.4 has a /sub?target=%TARGET%&url=%URL%&config=%CONFIG% API endpoint that accepts an arbitrary %URL% value and launches a GET request for it, but does not consider that the external request target may indirectly redirect back to this original /sub endpoint. Thus, a request loop and a denial of service may occur.

## Which versions are affected by CVE-2020-35579?

It affects 1 product.


Products: Subconverter Project Subconverter.

## How do I fix CVE-2020-35579?

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

## Is CVE-2020-35579 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-28927](https://insights.sbomify.com/CVE-2022-28927/): File upload in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-35579 and fix it if it is affected.

What it is: CVE-2020-35579 is a high-severity denial of service vulnerability in n/a, published on 20 Dec 2020. 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-2020-35579 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-2020-35579/ (Markdown: https://insights.sbomify.com/CVE-2020-35579/index.md)
```

## Sources

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

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