# CVE-2024-42531: Auth bypass in n/a

> Unauthenticated attackers can access live video streams from Ezviz PT cameras by crafting specific RTSP packets, bypassing authentication controls.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Aug 2024
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-wqgx-27v7-cr9h

## What is CVE-2024-42531?

CVE-2024-42531 is a critical authentication bypass vulnerability in n/a, published on 23 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Ezviz Internet PT Camera CS-CV246 D15655150 allows an unauthenticated host to access its live video stream by crafting a set of RTSP packets with a specific set of URLs that can be used to redirect the camera feed. NOTE: the vendor's perspective is that the Anonymous120386 sample code can establish RTSP protocol communictaion, but cannot obtain video or audio data; thus, there is no risk.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2024-42531?


## How do I fix CVE-2024-42531?

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

## Is CVE-2024-42531 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-42531 and fix it if it is affected.

What it is: CVE-2024-42531 is a critical authentication bypass vulnerability in n/a, published on 23 Aug 2024. 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-2024-42531 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-2024-42531/ (Markdown: https://insights.sbomify.com/CVE-2024-42531/index.md)
```

## Sources

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

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