# CVE-2022-22512: VARTA: Multiple devices prone to hard-coded credentials

> Hard-coded credentials in the Web-UI allow unauthorized attackers to gain administrative access to multiple VARTA Storage devices.

- **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:** 23 Mar 2023
- **Updated:** 25 Feb 2025
- **Also known as:** GHSA-cm5w-jvqg-v9cr

## What is CVE-2022-22512?

CVE-2022-22512 is a critical vulnerability in VARTA Storage Element S1, published on 23 Mar 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Hard-coded credentials in Web-UI of multiple VARTA Storage products in multiple versions allows an unauthorized attacker to gain administrative access to the Web-UI via network.

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

## Which versions are affected by CVE-2022-22512?

It affects 8 products.


Products: Varta Element Backup Firmware, Varta Element S1 Firmware, Varta Element S2 Firmware, Varta Element S3 Firmware, Varta Element S4 Firmware, Varta One L Firmware, Varta One Xl Firmware, Varta Pulse Firmware.

## How do I fix CVE-2022-22512?

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

## Is CVE-2022-22512 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-22512 and fix it if it is affected.

What it is: CVE-2022-22512 is a critical vulnerability in VARTA Storage Element S1, published on 23 Mar 2023. 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-2022-22512 in the wild and no public exploit code.

Affected product: VARTA Storage Element S1. 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-2022-22512/ (Markdown: https://insights.sbomify.com/CVE-2022-22512/index.md)
```

## Sources

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

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