dbcve.org
Cs141 FirmwareOperating system · Generex

CVE-2022-47188

HIGH · 7.5 CVSS v3.1 Published 2023-03-31
Fix available
A fix is available. Upgrade to 2.06 or later.
See remediation →
84/100
Remediation priority · High
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
There is an arbitrary file reading vulnerability in Generex UPS CS141 below 2.06 version. An attacker, making use of the default credentials, could upload a backup file containing a symlink to /etc/shadow, allowing him to obtain the content of this path.

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 · high confidence

Arbitrary file read vulnerability in Generex UPS CS141 devices below version 2.06 allows authenticated attackers to read sensitive system files by uploading a backup file containing a symbolic link to arbitrary paths such as /etc/shadow. The attacker exploits the default credentials to authenticate and then leverages the backup restoration functionality which does not sanitize symlinks in backup files.

MitigationUpdate Generex UPS CS141 to firmware version 2.06 or later to patch the vulnerability, and change the default credentials immediately to prevent unauthenticated or low-privilege access.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 device's web management interface or check physical labeling to confirm it is a Generex UPS CS141 device. Look for 'CS141' or 'Generex' markings on the device or in the admin interface header.
    Affected if The device is NOT a Generex CS141 unit - if it is a different model, this CVE does not apply.
  2. Determine the firmware version
    Log into the web interface and navigate to the System Information or About page. Alternatively, check via CLI if available. Note the exact firmware version number displayed.
    Affected if Firmware version is less than 2.06 (for example, 2.05, 2.04, 2.03, etc.). Versions 2.06 and above are patched.
  3. Verify backup restoration feature accessibility
    Locate the backup/restore functionality in the web interface, typically under Administration, Maintenance, or Backup Settings. Confirm the feature is present and accessible to your administrative account.
    Affected if The backup restoration feature exists and is accessible - this is the attack vector that must be present.
  4. Assess network exposure
    Determine if the device's web management interface is exposed to the network (not isolated on a trusted internal segment) or accessible remotely.
    Affected if The management interface is network-accessible - an attacker would need this access to authenticate and exploit.

You are affected if you have a Generex CS141 device running firmware version below 2.06 with an accessible backup restoration feature on a network-reachable management interface.

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

Update Generex UPS CS141 to firmware version 2.06 or later to patch the vulnerability, and change the default credentials immediately to prevent unauthenticated or low-privilege access.

Recommended fix High confidence

Generex CS141 Firmware 2.06 or later

  1. Obtain the Generex CS141 firmware version 2.06 or later from the official vendor website (www.generex.de)
  2. Review the vendor's official firmware upgrade documentation for the CS141 device
  3. Ensure the device is connected to a stable power source before initiating the firmware update
  4. Access the Generex CS141 web interface using administrative credentials
  5. Navigate to the firmware update or maintenance section
  6. Upload and apply the firmware version 2.06 or later following the vendor's documented procedure
  7. After successful upgrade, verify the firmware version has been updated
  8. As a security best practice, change the default administrative credentials to strong, unique passwords
Caveat Firmware upgrades carry inherent risks; ensure proper backup of configuration and test in a non-production environment before deploying to production UPS devices

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

Fix this in Cs141 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-47188 — 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-47188 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