# CVE-2024-35344: Hardcoded credentials in n/a

> Attackers can exploit hardcoded cryptographic keys in Anpviz IP camera firmware to bypass security controls and access sensitive data.

- **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 May 2024
- **Updated:** 13 Feb 2025

## What is CVE-2024-35344?

CVE-2024-35344 is a critical vulnerability in n/a, published on 28 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Certain Anpviz products contain a hardcoded cryptographic key stored in the firmware of the device. This affects IPC-D250, IPC-D260, IPC-B850, IPC-D850, IPC-D350, IPC-D3150, IPC-D4250, IPC-D380, IPC-D880, IPC-D280, IPC-D3180, MC800N, YM500L, YM800N_N2, YMF50B, YM800SV2, YM500L8, and YM200E10 firmware v3.2.2.2 and lower and possibly more vendors/models of IP camera.

Weakness: CWE-321 (Use of Hard-coded Cryptographic Key)

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


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

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

## Is CVE-2024-35344 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-35344 is a critical vulnerability in n/a, published on 28 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-35344 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-2024-35344/ (Markdown: https://insights.sbomify.com/CVE-2024-35344/index.md)
```

## Sources

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

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