# CVE-2020-36365: Open redirect in n/a

> Attackers can redirect users to malicious sites via vulnerable controller endpoints in Smartstore, potentially facilitating phishing attacks.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 19 May 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-5fmf-v8w4-327v

## What is CVE-2020-36365?

CVE-2020-36365 is a medium-severity vulnerability in n/a, published on 19 May 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Smartstore (aka SmartStoreNET) before 4.1.0 allows CommonController.ClearCache, ClearDatabaseCache, RestartApplication, and ScheduleTaskController.Edit open redirect.

Weakness: CWE-601 (URL Redirection to Untrusted Site)

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

It affects 1 product.


Products: Smartstore Smartstorenet.

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

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

## Is CVE-2020-36365 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-36365 exists.

Public exploit code:

- Smartstore <4.1.0 - Open Redirect (nuclei): http/cves/2020/CVE-2020-36365.yaml

## Other vulnerabilities in n/a

- [CVE-2020-36364](https://insights.sbomify.com/CVE-2020-36364/): Path traversal in n/a (critical 9.1)
- [CVE-2020-27997](https://insights.sbomify.com/CVE-2020-27997/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2020-27996](https://insights.sbomify.com/CVE-2020-27996/): Other in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-36365 is a medium-severity vulnerability in n/a, published on 19 May 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2020-36365 exists.

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-36365/ (Markdown: https://insights.sbomify.com/CVE-2020-36365/index.md)
```

## Sources

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

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