# CVE-2021-26627: EDrhyme QCP 200W Information Exposure Vulnerability

> Remote attackers can access live video feeds from EDrhyme QCP 200W cameras due to insufficient authentication on the RTSP port.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/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:** 19 Apr 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-8xw8-ghg5-7c3p

## What is CVE-2021-26627?

CVE-2021-26627 is a high-severity missing authorization vulnerability in EDrhyme Co.,Ltd QCP 200W, published on 19 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Real-time image information exposure is caused by insufficient authentication for activated RTSP port. This vulnerability could allow to remote attackers to send the RTSP requests using ffplay command and lead to leakage a live image.

Weakness: CWE-287 (Improper Authentication), CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Qcp Qcp200w Firmware.

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

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

## Is CVE-2021-26627 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2021-26627 is a high-severity missing authorization vulnerability in EDrhyme Co.,Ltd QCP 200W, published on 19 Apr 2022. 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-2021-26627 in the wild and no public exploit code.

Affected product: EDrhyme Co.,Ltd QCP 200W. 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-26627/ (Markdown: https://insights.sbomify.com/CVE-2021-26627/index.md)
```

## Sources

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

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