CVE-2022-0902
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 · uneditedImproper Limitation of a Pathname to a Restricted Directory ('Path Traversal'), Improper Neutralization of Special Elements used in a Command ('Command Injection') vulnerability in flow computer and remote controller products of ABB ( RMC-100 (Standard), RMC-100-LITE, XIO, XFCG5 , XRCG5 , uFLOG5 , UDC) allows an attacker who successfully exploited this vulnerability could insert and run arbitrary code in an affected system node.
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 confidenceCVE-2022-0902 is a critical path traversal and command injection vulnerability affecting ABB RMC-100, RMC-100-LITE, XIO, XFCG5, XRCG5, uFLOG5, and UDC flow computer and remote controller devices. The vulnerability allows authenticated or unauthenticated attackers to inject and execute arbitrary code on affected system nodes due to improper input validation and path sanitization.
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< 2105457-037< 2106229-011< 2106198-008< 2105805-016< 2105864-016< 2105298-024< 2106177-007CVSS 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 ABB device modelAccess the device web interface or check the device nameplate/documentation to confirm the exact model (RMC-100, RMC-100-LITE, XIO, XFCG5, XRCG5, UFLOC5, or UDC)Affected if The device is any of these seven models
-
Determine the firmware versionLog into the device administrative interface or use the vendor-specific management tool to view the installed firmware version. The version is typically found under System Info, Device Status, or Firmware Update sectionsAffected if The firmware version falls below the threshold for your specific model (RMC-100 < 2105457-037, RMC-100-LITE < 2106229-011, XIO < 2106198-008, XFCG5 < 2105805-016, XRCG5 < 2105864-016, UFLOC5 < 2105298-024, or UDC < 2106177-007)
-
Verify web management interface exposureCheck network configuration to determine if the device web interface (HTTP/HTTPS ports) is accessible from external networks or untrusted zones rather than only from an isolated management VLANAffected if The management interface is exposed to untrusted networks (this increases exploitability for both authenticated and unauthenticated attack vectors)
-
Inspect for unauthorized access or changesReview device logs, audit trails, or system event logs for unusual commands, unexpected file access patterns, or modifications to configuration files that may indicate exploitation attemptsAffected if Logs show suspicious path traversal patterns or unexpected command executions
A user is affected if they have any of the listed ABB device models running firmware versions below the specified thresholds, particularly if the management interface is network-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 · scoped2105298-0242105457-0372105805-016
Apply vendor-supplied firmware updates from ABB; if patches are unavailable, implement network segmentation to isolate affected devices and deploy IDS/IPS rules to detect exploitation attempts. Restrict external access to management interfaces.
Firmware version equal to or greater than: 2105457-037 (RMC-100), 2106229-011 (RMC-100-LITE), 2106198-008 (XIO), 2105805-016 (XFCG5), 2105864-016 (XRCG5), 2105298-024 (uFLOG5), 2106177-007 (UDC)
- 1. Identify the specific ABB product model (RMC-100, RMC-100-LITE, XIO, XFCG5, XRCG5, uFLOG5, or UDC) in your environment
- 2. Check the current firmware version of the affected device through its management interface
- 3. Navigate to ABB's official support portal at search.abb.com to download the latest firmware
- 4. For RMC-100: upgrade to firmware version 2105457-037 or later
- 5. For RMC-100-LITE: upgrade to firmware version 2106229-011 or later
- 6. For XIO: upgrade to firmware version 2106198-008 or later
- 7. For XFCG5: upgrade to firmware version 2105805-016 or later
- 8. For XRCG5: upgrade to firmware version 2105864-016 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation12.0 h
- Implementation20.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-0902 — 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-0902 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