# CVE-2023-48121: Auth bypass in n/a

> Remote attackers can bypass authentication in Ezviz cameras to obtain sensitive information via crafted messages.

- **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:** 28 Nov 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-9rc5-4p7c-qp9h

## What is CVE-2023-48121?

CVE-2023-48121 is a medium-severity authentication bypass vulnerability in n/a, published on 28 Nov 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An authentication bypass vulnerability in the Direct Connection Module in Ezviz CS-C6N-xxx prior to v5.3.x build 20230401, Ezviz CS-CV310-xxx prior to v5.3.x build 20230401, Ezviz CS-C6CN-xxx prior to v5.3.x build 20230401, Ezviz CS-C3N-xxx prior to v5.3.x build 20230401 allows remote attackers to obtain sensitive information by sending crafted messages to the affected devices.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2023-48121?

It affects 4 products.


Products: Ezviz Cs-C3n-A0-3h2wfrl Firmware, Ezviz Cs-C6cn-A0-3h2wfr Firmware, Ezviz Cs-C6n-A0-1c2wfr Firmware, Ezviz Cs-Cv310-A0-1c2wfr Firmware.

## How do I fix CVE-2023-48121?

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

## Is CVE-2023-48121 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-48121 and fix it if it is affected.

What it is: CVE-2023-48121 is a medium-severity authentication bypass vulnerability in n/a, published on 28 Nov 2023. 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-2023-48121 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-2023-48121/ (Markdown: https://insights.sbomify.com/CVE-2023-48121/index.md)
```

## Sources

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

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