dbcve.org
Rapid ScadaApplication · Rapidscada

CVE-2024-21869

MEDIUM · 5.5 CVSS v3.1 Published 2024-02-02
Fix available
A fix is available. Upgrade to after 5.8.4 or later.
See remediation →
57/100
Remediation priority · Elevated
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
In Rapid Software LLC's Rapid SCADA versions prior to Version 5.8.4, the affected product stores plaintext credentials in various places. This may allow an attacker with local access to see them.

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

Rapid SCADA versions prior to 5.8.4 store user credentials in plaintext across multiple locations on the system. An attacker with local access to the server can read these plaintext credentials, potentially enabling unauthorized access to the SCADA system and its functionalities.

MitigationUpgrade to Rapid SCADA Version 5.8.4 or later, which addresses the plaintext credential storage. Additionally, rotate any credentials that may have been exposed and restrict physical and local access to the server hosting Rapid SCADA.

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
Rapid ScadaApplication
Affected:<= 5.8.4

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

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. Locate Rapid SCADA installation directory
    Check common installation paths such as C:\Program Files\Rapid SCADA or C:\SCADA, or search for directories containing 'Scada' in the name on the server file system.
    Affected if Rapid SCADA software is found installed on the system
  2. Determine installed Rapid SCADA version
    Locate version information in the installation directory, typically found in application files, assembly info, or a version.txt file. Compare your installed version to the affected range of versions <= 5.8.4.
    Affected if The installed version is 5.8.4 or earlier
  3. Identify credential storage locations
    Search the Rapid SCADA installation directory and associated data folders for configuration files that store user credentials, such as user database files, XML configuration files, or settings files that may contain authentication data.
    Affected if Credential storage files exist in the Rapid SCADA directory structure
  4. Inspect credential files for plaintext storage
    Open and examine the identified credential storage files using a text editor or file viewer. Look for visible, unencrypted username and password pairs stored in plain text format rather than in hashed or encrypted form.
    Affected if User credentials are stored in plaintext (readable, unencrypted format) within configuration or database files

The environment is affected if Rapid SCADA version 5.8.4 or earlier is installed AND plaintext credentials are found in configuration or database files within the Rapid SCADA installation directory.

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 a release after 5.8.4
Interim mitigation

Upgrade to Rapid SCADA Version 5.8.4 or later, which addresses the plaintext credential storage. Additionally, rotate any credentials that may have been exposed and restrict physical and local access to the server hosting Rapid SCADA.

Recommended fix High confidence

Version 5.8.4

  1. Backup the Rapid SCADA installation directory and database before proceeding
  2. Download Rapid SCADA Version 5.8.4 from the official source at rapidscada.org
  3. Stop the Rapid SCADA service to prevent data inconsistency during upgrade
  4. Install or apply the Version 5.8.4 upgrade following standard installation procedures
  5. After installation, verify that credentials are no longer stored in plaintext (the fixed version should use proper encryption)
  6. Start the Rapid SCADA service and confirm normal operation

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

Fix this in Rapid Scada Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing12.0 h
  • Review / QA6.0 h
50.0 hours of engineering $8,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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