CVE-2022-47190
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 webshell that could allow him to execute arbitrary code as root.
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 confidenceThe Generex UPS CS141 device versions below 2.06 contain an insecure firmware upload mechanism that lacks proper validation of uploaded firmware files. An attacker can craft a malicious firmware package containing a webshell and upload it to the device, then execute the webshell to achieve arbitrary code execution with root privileges.
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
- 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 device modelLocate the UPS device and confirm it is a Generex CS141 model by checking the device label, management interface, or SNMP inventoryAffected if The device is a Generex CS141 unit
-
Determine the installed firmware versionAccess the device's web management interface or use SNMP to query the firmware version information. Look for a version field in the system info or status pageAffected if The displayed firmware version is below 2.06 (e.g., 2.05, 2.04, etc.)
-
Verify if the web management interface is accessibleAttempt to reach the device's HTTP/HTTPS management portal from a network location. Check if port 80 or 443 (or configured alternative ports) respondAffected if The management interface is reachable over the network and accepts authentication
-
Confirm firmware upload functionality is presentLog into the device management interface and navigate to firmware update, upgrade, or maintenance sections. Look for a firmware upload or file import featureAffected if A firmware upload or upgrade page exists and accepts file uploads
A user is affected if they have a Generex CS141 device running firmware version 2.05 or lower, with the device's web management interface accessible and the firmware upload feature available.
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 to remediate this vulnerability. If upgrading is not immediately possible, restrict network access to the device's management interface and disable any unnecessary remote access features.
Firmware version 2.06
- 1. Visit the official Generex support website at www.generex.de to obtain the firmware version 2.06 or later for the CS141 device.
- 2. Review the device's current firmware version through the administrative web interface or console.
- 3. Create a backup of the current device configuration if the web interface provides export functionality.
- 4. Access the firmware update section in the device's administrative interface.
- 5. Upload the downloaded firmware file (version 2.06 or later) to the device.
- 6. Wait for the firmware upload and installation process to complete; do not power off the device during this process.
- 7. After the device reboots, verify that the new firmware version (2.06) is installed.
- 8. Confirm that the device is functioning normally and all services are operational.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-47190 — 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-47190 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