# CVE-2021-40149: Information disclosure in n/a

> An attacker can download the SSL private key from the E1 Zoom camera web server, compromising encrypted communications.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/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:** 17 Jul 2022
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-hq75-6wcm-hc6g

## What is CVE-2021-40149?

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

### Official description

The web server of the E1 Zoom camera through 3.0.0.716 discloses its SSL private key via the root web server directory. In this way an attacker can download the entire key via the /self.key URI.

Weakness: CWE-552 (Files or Directories Accessible to External Parties)

## Which versions are affected by CVE-2021-40149?

It affects 1 product.


Products: Reolink E1 Zoom Firmware.

## How do I fix CVE-2021-40149?

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

## Is CVE-2021-40149 being exploited?

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

Public exploit code:

- Reolink E1 Zoom Camera <=3.0.0.716 - Private Key Disclosure (nuclei): http/cves/2021/CVE-2021-40149.yaml

## Other vulnerabilities in n/a

- [CVE-2021-40150](https://insights.sbomify.com/CVE-2021-40150/): Information disclosure in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-40149 and fix it if it is affected.

What it is: CVE-2021-40149 is a medium-severity vulnerability in n/a, published on 17 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2021-40149 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-2021-40149/ (Markdown: https://insights.sbomify.com/CVE-2021-40149/index.md)
```

## Sources

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

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