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

> Attackers can enumerate valid usernames via distinct login responses, facilitating brute-force attacks against IP cameras.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/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:** 23 Jul 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-m67c-r98h-r497

## What is CVE-2020-11625?

CVE-2020-11625 is a medium-severity vulnerability in n/a, published on 23 Jul 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in AvertX Auto focus Night Vision HD Indoor/Outdoor IP Dome Camera HD838 and Night Vision HD Indoor/Outdoor Mini IP Bullet Camera HD438. Failed web UI login attempts elicit different responses depending on whether a user account exists. Because the responses indicate whether a submitted username is valid or not, they make it easier to identify legitimate usernames. If a login request is sent to ISAPI/Security/sessionLogin/capabilities using a username that exists, it will return the value of the salt given to that username, even if the password is incorrect. However, if a login request is sent using a username that is not present in the database, it will return an empty salt value. This allows attackers to enumerate legitimate usernames, facilitating brute-force attacks. NOTE: this is different from CVE-2020-7057.

Weakness: CWE-203 (Observable Discrepancy)

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

It affects 2 products.


Products: Avertx Hd438 Firmware, Avertx Hd838 Firmware.

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

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

## Is CVE-2020-11625 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-11624](https://insights.sbomify.com/CVE-2020-11624/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2020-11623](https://insights.sbomify.com/CVE-2020-11623/): Security feature bypass in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-11625 is a medium-severity vulnerability in n/a, published on 23 Jul 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-11625 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-11625/ (Markdown: https://insights.sbomify.com/CVE-2020-11625/index.md)
```

## Sources

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

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