CVE-2022-47191
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 · uneditedGenerex UPS CS141 below 2.06 version, could allow a remote attacker to upload a firmware file containing a file with modified permissions, allowing him to escalate privileges.
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 confidenceGenerex UPS CS141 devices below version 2.06 contain a firmware upload vulnerability that fails to properly validate file permissions within uploaded firmware packages. An attacker can upload a malicious firmware file containing executables or scripts with elevated permissions, achieving privilege escalation on the device.
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< 2.06CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 device modelLocate the UPS device and verify it is a Generex CS141 model. Check device labeling, web interface, or management console for the model number.Affected if The device is not a Generex UPS CS141 model, then this CVE does not apply.
-
Check the installed firmware versionAccess the device web interface, management console, or use SNMP to retrieve the firmware version. Compare the version number against 2.06.Affected if The installed firmware version is below 2.06 (e.g., 2.05, 2.04, etc.), indicating the device is vulnerable.
-
Verify firmware upload functionality is accessibleConfirm the device web interface or management interface has a firmware upload/update feature available and is accessible to the user or attacker.Affected if The firmware upload feature is enabled and accessible, making exploitation possible.
-
Check for unauthorized firmware filesInspect the device file system or backup configurations for any unexpected firmware files or modifications to firmware-related directories.Affected if Unexpected firmware files are present that were not authored by the administrator.
The environment is affected if the device is a Generex UPS CS141 running firmware version below 2.06 with the firmware upload feature accessible.
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 · scoped2.06
Upgrade the Generex UPS CS141 firmware to version 2.06 or later, which properly validates file permissions during the firmware upload process.
Generex CS141 Firmware version 2.06
- Obtain the Generex CS141 firmware version 2.06 from the official vendor website (www.generex.de) or authorized distribution channels
- Review the vendor's official firmware upgrade documentation for the CS141 device
- Upload and apply firmware version 2.06 to the Generex UPS CS141 device following the vendor's documented procedure
- Verify the firmware upgrade was successful by checking the device firmware version
- Confirm that the device operates normally after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation3.0 h
- Testing3.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 $3,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-47191 — 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-47191 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