# CVE-2020-35577: Missing authorization in n/a

> Authenticated users can download any uploaded file by manipulating the file identifier, exposing sensitive data.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Feb 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-233g-v6pm-h695

## What is CVE-2020-35577?

CVE-2020-35577 is a medium-severity missing authorization vulnerability in n/a, published on 18 Feb 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In Endalia Selection Portal before 4.205.0, an Insecure Direct Object Reference (IDOR) allows any authenticated user to download every file uploaded to the platform by changing the value of the file identifier (aka CommonDownload identification number).

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

It affects 1 product.


Products: Endalia Selection Portal.

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

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

## Is CVE-2020-35577 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-35577 is a medium-severity missing authorization vulnerability in n/a, published on 18 Feb 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-35577 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-35577/ (Markdown: https://insights.sbomify.com/CVE-2020-35577/index.md)
```

## Sources

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

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