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

> Vinchin Backup & Recovery uses default root credentials, allowing attackers to gain administrative access and potentially execute code.

- **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:** 2 Feb 2024
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-97vr-j4hr-qrq8

## What is CVE-2024-22902?

CVE-2024-22902 is a critical vulnerability in n/a, published on 2 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vinchin Backup & Recovery v7.2 was discovered to be configured with default root credentials.

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

It affects 1 product.


Products: Vinchin Vinchin Backup and Recovery.

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

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

## Is CVE-2024-22902 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-22901](https://insights.sbomify.com/CVE-2024-22901/): 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-2023-45499](https://insights.sbomify.com/CVE-2023-45499/): Hardcoded credentials 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-2024-22902 and fix it if it is affected.

What it is: CVE-2024-22902 is a critical vulnerability in n/a, published on 2 Feb 2024. 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-2024-22902 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-22902/ (Markdown: https://insights.sbomify.com/CVE-2024-22902/index.md)
```

## Sources

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

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