# CVE-2024-54849: Weak cryptography in n/a

> Attackers can obtain the second RSA private key to access sensitive data or perform man-in-the-middle attacks on CP Plus NVR devices.

- **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:** 10 Jan 2025
- **Updated:** 13 Jan 2025
- **Also known as:** GHSA-f9mx-3gv3-xr48

## What is CVE-2024-54849?

CVE-2024-54849 is a medium-severity vulnerability in n/a, published on 10 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue in CP Plus CP-VNR-3104 B3223P22C02424 allows attackers to obtain the second RSA private key and access sensitive data or execute a man-in-the-middle attack.

Weakness: CWE-295 (Improper Certificate Validation)

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

It affects 1 product.


Products: Cpplusworld Cp-Vnr-3104 Firmware.

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

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

## Is CVE-2024-54849 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-3705](https://insights.sbomify.com/CVE-2023-3705/): Information Disclosure Vulnerability in CP-Plus Network Video Recorder (high 7.5)
- [CVE-2024-54848](https://insights.sbomify.com/CVE-2024-54848/): Weak cryptography in n/a (high 7.4)
- [CVE-2024-54846](https://insights.sbomify.com/CVE-2024-54846/): Weak cryptography in n/a (medium 5.9)
- [CVE-2024-54847](https://insights.sbomify.com/CVE-2024-54847/): Weak cryptography in n/a (medium 5.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-54849 is a medium-severity vulnerability in n/a, published on 10 Jan 2025. 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-54849 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-54849/ (Markdown: https://insights.sbomify.com/CVE-2024-54849/index.md)
```

## Sources

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

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