CVE-2022-22512
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedHard-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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceHard-coded credentials embedded in the Web-UI of VARTA Storage products allow unauthenticated remote attackers to gain administrative access to the system via network. The credentials are present in multiple software versions.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< f21000400< 2e.3.8.0< 2e.3.8.0< 2e.3.8.0>= 2e.4.0.0, < 2e.4.4.0< d21010400< 2e.3.8.0< 2e.3.8.0< c21010800CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the VARTA Storage product modelLog into the device Web-UI or check the physical device label to determine the exact model (e.g., Varta Element S1, Varta Pulse, Varta One XL). The model name is typically displayed in the Web-UI header or system information page.Affected if The product model is any of: Varta Element Backup, Varta Element S1, Varta Element S2, Varta Element S3, Varta Element S4, Varta One L, Varta One Xl, or Varta Pulse.
-
Locate the firmware version in the Web-UINavigate to the device Web-UI administrative interface. Look for a System Info, About, or Firmware Version page typically found under Settings, Maintenance, or System sections. Record the displayed firmware version number.Affected if This step confirms the installed firmware version for comparison against the vulnerable ranges.
-
Compare installed version to affected ranges for Element BackupIf the product is Varta Element Backup, compare your firmware version against the vulnerable range: versions below f21000400 are affected.Affected if Installed version is less than f21000400.
-
Compare installed version to affected ranges for Element S1/S2/One L/One XLIf the product is Varta Element S1, S2, Varta One L, or Varta One XL, compare your firmware version against the vulnerable range: versions below 2e.3.8.0 are affected.Affected if Installed version is less than 2e.3.8.0.
-
Compare installed version to affected ranges for Element S3If the product is Varta Element S3, compare your firmware version. Versions below 2e.3.8.0 are affected, AND versions from 2e.4.0.0 up to but not including 2e.4.4.0 are also affected.Affected if Installed version is less than 2e.3.8.0, OR installed version is >= 2e.4.0.0 and less than 2e.4.4.0.
-
Compare installed version to affected ranges for Element S4 and PulseIf the product is Varta Element S4, versions below d21010400 are affected. If Varta Pulse, versions below c21010800 are affected.Affected if For Element S4: installed version is less than d21010400. For Pulse: installed version is less than c21010800.
The environment is affected if the identified product model matches any Varta Storage product listed and the installed firmware version falls within any of the specified vulnerable version ranges.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2e.3.8.02e.4.4.0
Apply vendor-supplied firmware updates that remove hard-coded credentials; if unavailable, contact VARTA for credential rotation procedures or implement network segmentation to restrict Web-UI access.
Element Backup: f21000400 or later | Element S1: 2e.3.8.0 or later | Element S2: 2e.3.8.0 or later | Element S3: 2e.3.8.0 to 2e.3.8.0 or later (or >= 2e.4.4.0 if previously on 2e.4.x) | Element S4: d21010400 or later | One L: 2e.3.8.0 or later | One XL: 2e.3.8.0 or later | Pulse: c21010800 or later
- 1. Identify the specific VARTA Storage product model (Element Backup, Element S1, S2, S3, S4, One L, One XL, or Pulse) from the affected device.
- 2. Determine the current firmware version running on the device through the Web-UI or device documentation.
- 3. Download the latest firmware version from the official VARTA Storage website or contact VARTA support for the firmware update.
- 4. Follow the manufacturer's firmware update instructions to apply the upgrade, ensuring stable power during the process.
- 5. After upgrading, verify the firmware version matches or exceeds the fixed release for your product model.
- 6. Change any default credentials if prompted during or after the update, and ensure strong, unique passwords are used.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22512 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-22512 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data