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

> Attackers can use hardcoded credentials to gain unauthorized access to VinChin Backup & Recovery systems, potentially compromising data.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Oct 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-gj84-56mj-c85j

## What is CVE-2023-45499?

CVE-2023-45499 is a critical vulnerability in n/a, published on 27 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

VinChin Backup & Recovery v5.0.*, v6.0.*, v6.7.*, and v7.0.* was discovered to contain hardcoded credentials.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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

It affects 1 product.


Products: Vinchin Vinchin Backup and Recovery.

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

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

## Is CVE-2023-45499 being exploited?

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

Public exploit code:

- Vinchin Backup and Recovery Command Injection (metasploit)

## Other vulnerabilities in n/a

- [CVE-2024-22901](https://insights.sbomify.com/CVE-2024-22901/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2024-22902](https://insights.sbomify.com/CVE-2024-22902/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2023-45498](https://insights.sbomify.com/CVE-2023-45498/): Command injection in n/a (critical 9.8)
- [CVE-2022-35866](https://insights.sbomify.com/CVE-2022-35866/): Hardcoded credentials in Backup and Recovery (critical 9.8)
- [CVE-2024-25228](https://insights.sbomify.com/CVE-2024-25228/): Command injection in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-45499 is a critical vulnerability in n/a, published on 27 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-45499 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-2023-45499/ (Markdown: https://insights.sbomify.com/CVE-2023-45499/index.md)
```

## Sources

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

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