# CVE-2020-9389: Information disclosure in n/a

> Attackers can enumerate valid usernames in SquaredUp by analyzing response time differences during login attempts.

- **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Feb 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-f8pq-r7mv-pvxm

## What is CVE-2020-9389?

CVE-2020-9389 is a low-severity vulnerability in n/a, published on 3 Feb 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A username enumeration issue was discovered in SquaredUp before version 4.6.0. The login functionality was implemented in a way that would enable a malicious user to guess valid username due to a different response time from invalid usernames.

Weakness: CWE-203 (Observable Discrepancy)

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

It affects 1 product.


Products: Squaredup Squaredup.

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

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

## Is CVE-2020-9389 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-40091](https://insights.sbomify.com/CVE-2021-40091/): Server-side request forgery in n/a (critical 9.8)
- [CVE-2020-9388](https://insights.sbomify.com/CVE-2020-9388/): Cross-site request forgery in n/a (medium 6.5)
- [CVE-2021-40092](https://insights.sbomify.com/CVE-2021-40092/): Cross-site scripting in n/a (medium 5.4)
- [CVE-2021-40093](https://insights.sbomify.com/CVE-2021-40093/): Cross-site scripting in n/a (medium 5.4)
- [CVE-2021-40094](https://insights.sbomify.com/CVE-2021-40094/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-9389 is a low-severity vulnerability in n/a, published on 3 Feb 2021. 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-9389 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-9389/ (Markdown: https://insights.sbomify.com/CVE-2020-9389/index.md)
```

## Sources

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

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