# CVE-2024-5632: Hardcoded credentials in NVR3608PGE2W

> Attackers can access the device's WiFi network using a default password that is not changed during installation, potentially compromising video feeds.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Jul 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-w7rr-wm5c-6w59

## What is CVE-2024-5632?

CVE-2024-5632 is a medium-severity vulnerability in Longse Technology NVR3608PGE2W, published on 9 Jul 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Longse NVR (Network Video Recorder) model NVR3608PGE2W, as well as products based on this device, create a WiFi network with a default password.
A user is neither advised to change it during the installation process, nor such a need is described in the manual. As the cameras from the same kit connect automatically, it is very probable for the default password to be left unchanged.

Weakness: CWE-1392 (Use of Default Credentials)

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


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

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

## Is CVE-2024-5632 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-5632 is a medium-severity vulnerability in Longse Technology NVR3608PGE2W, published on 9 Jul 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-5632 in the wild and no public exploit code.

Affected product: Longse Technology NVR3608PGE2W. 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-5632/ (Markdown: https://insights.sbomify.com/CVE-2024-5632/index.md)
```

## Sources

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

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