dbcve.org
Cs141 FirmwareOperating system · Generex

CVE-2022-47189

CRITICAL · 9.1 CVSS v3.1 Published 2023-03-31
Fix available
A fix is available. Upgrade to 2.06 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Generex UPS CS141 below 2.06 version, allows an attacker toupload a firmware file containing an incorrect configuration, in order to disrupt the normal functionality of the device.

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 confidence

The Generex UPS CS141 device below version 2.06 contains a vulnerability in its firmware upload mechanism that lacks proper authentication and validation checks. This allows an unauthenticated attacker to upload malicious firmware files containing incorrect configurations, causing disruption to the UPS device's normal functionality.

MitigationUpgrade the Generex UPS CS141 firmware to version 2.06 or later, and implement cryptographic integrity verification and authentication for all firmware uploads to prevent similar attacks.

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
Cs141 FirmwareOperating system
Affected:< 2.06

CVSS 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
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Access the UPS management interface (web GUI, console, or SNMP) and confirm the device is a Generex UPS CS141. Check the device inventory or network discovery results for the exact model identifier.
    Affected if The device is not a Generex UPS CS141 (different models are not affected by this specific CVE)
  2. Check the installed firmware version
    Locate the firmware version information in the device's web interface (typically under System, Status, or About section), console CLI (often via 'show version' or 'system info' command), or via SNMP OID. Compare the version number to 2.06.
    Affected if The installed firmware version is below 2.06 (e.g., 2.05, 2.04, 1.x)
  3. Verify firmware upload interface accessibility
    Attempt to access the firmware upload or firmware upgrade page in the device web interface, or check if the upload endpoint responds to requests. Note whether any authentication is prompted before reaching the upload functionality.
    Affected if The firmware upload page is accessible without requiring authentication credentials, indicating the vulnerable unauthenticated upload mechanism is present
  4. Inspect firmware upload configuration
    Review the device configuration for firmware upgrade settings. Check if there are any authentication requirements, integrity verification flags, or upload restrictions defined in the device settings or configuration file.
    Affected if No authentication requirement is enforced for firmware uploads, or integrity verification is disabled/missing in the configuration

A user is affected if they have a Generex UPS CS141 device running firmware version below 2.06 with an unauthenticated firmware upload interface accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2.06 or later
Fixed in 2.06
Interim mitigation

Upgrade the Generex UPS CS141 firmware to version 2.06 or later, and implement cryptographic integrity verification and authentication for all firmware uploads to prevent similar attacks.

Recommended fix Moderate confidence

Firmware 2.06

  1. 1. Visit the official Generex support website at www.generex.de to obtain the firmware version 2.06 or later for the CS141 UPS device.
  2. 2. Review the firmware release notes to understand any installation prerequisites or注意事项.
  3. 3. Backup the current device configuration if possible.
  4. 4. Access the CS141 device management interface using authorized administrative credentials.
  5. 5. Navigate to the firmware update section of the management interface.
  6. 6. Upload the downloaded firmware file (version 2.06 or later).
  7. 7. Follow the on-screen instructions to complete the firmware upgrade process.
  8. 8. Verify the firmware version after upgrade to confirm version 2.06 or later is installed.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cs141 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,840
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-47189 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-47189 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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