dbcve.org
RccmdApplication · Abb

CVE-2022-4126

CRITICAL · 9.8 CVSS v3.1 Published 2023-03-27
Fix available
A fix is available. Upgrade to 4.40_230207 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Use of Default Password vulnerability in ABB RCCMD on Windows, Linux, MacOS allows Try Common or Default Usernames and Passwords.This issue affects RCCMD: before 4.40 230207.

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

Use of default password vulnerability in ABB RCCMD (Remote Console Command) software across Windows, Linux, and MacOS platforms. The software ships with default credentials that can be exploited by attackers using common or default username/password combinations to gain unauthorized access.

MitigationUpdate ABB RCCMD to version 4.40 230207 or later, which removes or remediates the default password issue. If already deployed, immediately change any default credentials and verify no unauthorized access has occurred.

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
RccmdApplication
Affected:< 4.40_230207

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if ABB RCCMD is installed
    Look for RCCMD installation directories or running processes. On Windows check Program Files, on Linux/Mac check common installation paths like /opt/rccmd or /usr/local/rccmd. Also check for rccmd processes running (rccmd.exe on Windows, rccmd on Linux/Mac).
    Affected if RCCMD software is found running or installed on the system
  2. Identify the installed RCCMD version
    Check the version of the installed RCCMD binary or check version information in the software's about section, configuration files, or by running 'rccmd --version' if supported. Compare the version number to 4.40_230207.
    Affected if The installed version is lower than 4.40_230207
  3. Locate and inspect RCCMD configuration files
    Examine RCCMD configuration files (typically found in the RCCMD installation directory or config subfolder) for stored username and password entries. Look for any credential-related configuration sections.
    Affected if Configuration files contain username/password entries using default or common values
  4. Verify if default credentials are in use
    Check if the username and password in the RCCMD configuration match commonly documented default credentials for this software. Default credentials often use simple or well-known combinations.
    Affected if The configured credentials match known default username/password combinations for RCCMD

A user is affected if they have ABB RCCMD installed with a version lower than 4.40_230207 AND the software is configured to use default credentials.

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 4.40_230207 or later
Fixed in 4.40_230207
Interim mitigation

Update ABB RCCMD to version 4.40 230207 or later, which removes or remediates the default password issue. If already deployed, immediately change any default credentials and verify no unauthorized access has occurred.

Recommended fix High confidence

RCCMD version 4.40_230207

  1. Identify the current installed version of ABB RCCMD on the system (Windows, Linux, or MacOS)
  2. Download ABB RCCMD version 4.40_230207 or later from the official ABB website (search.abb.com)
  3. Backup the existing RCCMD configuration files before upgrading
  4. Stop the RCCMD service if it is currently running
  5. Install the new version (4.40_230207 or later) over the existing installation
  6. After installation, verify the new version is correctly installed
  7. Change the default password to a strong, unique password following ABB's password guidelines
  8. Restart the RCCMD service
Caveat Review release notes for any configuration changes between old version and 4.40_230207

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

Fix this in Rccmd Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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