CyberSecBulletin
CVE-2022-0902NVD status: Modified

RMC-100 (Standard): Improper Limitation of a Pathname to a Restricted Directory

CVE-2022-0902 is a critical-severity improper limitation of a pathname to a restricted directory vulnerability in RMC-100 (Standard) from ABB, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version 2105457-037 as the first without the flaw, so updating RMC-100 (Standard) to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 16.9% chance of exploitation within 30 days, which is in the top 2.89% of all scored CVEs.

Patch this week

Critical severity: a successful attack would have severe impact.

What to do

  1. Update RMC-100 (Standard) to 2105457-037 or a later version.
  2. Update RMC-100-LITE to 2106229-011 or a later version.
  3. Update XIO to 2106198-008 or a later version.
  4. Read the advisory on search.abb.com for workarounds and exact fixed builds.
  5. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
ABBRMC-100 (Standard)before 2105457-0372105457-037
ABBRMC-100-LITEbefore 2106229-0112106229-011
ABBXIObefore 2106198-0082106198-008
ABBXFCG5before 2105805-0162105805-016
ABBXRCG5before 2105864-0162105864-016
ABBuFLOG5before 2105298-0242105298-024
ABBUDCbefore 2106177-0072106177-007
ABBRmc-100 Firmwarebefore 2105457-0372105457-037
ABBRmc-100-lite Firmwarebefore 2106229-0112106229-011
ABBXio Firmwarebefore 2106198-0082106198-008
ABBXfcg5 Firmwarebefore 2105805-0162105805-016
ABBXrcg5 Firmwarebefore 2105864-0162105864-016
ABBUflog5 Firmwarebefore 2105298-0242105298-024
ABBUdc Firmwarebefore 2106177-0072106177-007

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.18.1HighCNA (ch.abb.com)
CVSS 3.19.8CriticalNVD

Official description

Improper 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.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Improper Limitation of a Pathname to a Restricted Directory

The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.

How developers prevent this class of flaw

  • For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
  • Use an application firewall that can detect attacks against this weakness. It can be beneficial in cases in which the code cannot be fixed (because it is controlled by a third party), as an emergency prevention measure while more comprehensive software assurance measures are applied, or to provide defense in depth.

More Improper Limitation of a Pathname to a Restricted Directory vulnerabilities (CWE-22)

Timeline

  1. CVE record published.
  2. Record last changed materially (score, affected products, status or references).

References

Recent Improper Limitation of a Pathname to a Restricted Directory vulnerabilities

Spotted an error? Tell us.