# CVE-2023-41610: Hardcoded credentials in n/a

> An attacker can gain root access to the Victure PC420 camera using a hardcoded plaintext password, leading to full device compromise.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Sep 2024
- **Updated:** 18 Sep 2024
- **Also known as:** GHSA-9387-xrfr-3wfr

## What is CVE-2023-41610?

CVE-2023-41610 is a high-severity vulnerability in n/a, published on 18 Sep 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Victure PC420 1.1.39 was discovered to contain a hardcoded root password which is stored in plaintext.

Weakness: CWE-798 (Use of Hard-coded Credentials), CWE-256 (Plaintext Storage of a Password)

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

It affects 1 product.


Products: Govicture Pc420 Firmware.

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

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

## Is CVE-2023-41610 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-15744](https://insights.sbomify.com/CVE-2020-15744/): Stack-based buffer overflow leading to RCE in Victure Camera (critical 9.6)
- [CVE-2023-41612](https://insights.sbomify.com/CVE-2023-41612/): Hardcoded credentials in n/a (high 8.8)
- [CVE-2023-41611](https://insights.sbomify.com/CVE-2023-41611/): Hardcoded credentials in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-41610 is a high-severity vulnerability in n/a, published on 18 Sep 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-2023-41610 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-41610/ (Markdown: https://insights.sbomify.com/CVE-2023-41610/index.md)
```

## Sources

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

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