dbcve.org
Rapid ScadaApplication · Rapidscada

CVE-2024-21764

CRITICAL · 9.8 CVSS v3.1 Published 2024-02-02
Fix available
A fix is available. Upgrade to after 5.8.4 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
In Rapid Software LLC's Rapid SCADA versions prior to Version 5.8.4, the product uses hard-coded credentials, which may allow an attacker to connect to a specific port.

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 confidence

Rapid SCADA versions prior to 5.8.4 contain hard-coded credentials embedded in the software that allow unauthorized attackers to authenticate to a specific port, bypassing normal authentication controls. This critical vulnerability enables remote unauthenticated access with a CVSS 9.8 severity rating.

MitigationUpgrade to Rapid SCADA Version 5.8.4 or later to remove the hardcoded credentials. If immediate patching is not possible, network segmentation and firewall rules restricting access to the affected port should be implemented as a compensating control.

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
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. Determine installed Rapid SCADA version
    Locate the Rapid SCADA installation directory and check the version information, typically found in the application properties, about screen, or version file within the installation folder
    Affected if The installed version is 5.8.4 or any version prior to 5.8.4
  2. Identify open ports used by Rapid SCADA
    Use netstat or a port scanning tool to list all ports on which Rapid SCADA services are listening
    Affected if Rapid SCADA services are listening on any port and the version is vulnerable (5.8.4 or prior)
  3. Verify network accessibility of Rapid SCADA ports
    Review firewall rules and network configuration to determine which Rapid SCADA ports are exposed to untrusted networks or the internet
    Affected if Any Rapid SCADA port is accessible from untrusted networks while running a vulnerable version
  4. Test for unauthenticated access capability
    Attempt to connect to the Rapid SCADA service ports without providing credentials to verify whether authentication can be bypassed
    Affected if Unauthenticated access is granted to any Rapid SCADA service without valid credentials on a vulnerable version

The environment is affected if Rapid SCADA version 5.8.4 or earlier is installed and any service port is network-accessible, due to the hardcoded credentials allowing bypass of normal authentication.

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 to remove the hardcoded credentials. If immediate patching is not possible, network segmentation and firewall rules restricting access to the affected port should be implemented as a compensating control.

Recommended fix High confidence

Version 5.8.4

  1. Create a full backup of the current Rapid SCADA installation, including configuration files and databases
  2. Download Rapid SCADA version 5.8.4 or later from the official source (rapidscada.org)
  3. Stop the Rapid SCADA services before upgrading
  4. Install version 5.8.4 following the official upgrade documentation
  5. Restore the configuration from the backup after installation
  6. Start the Rapid SCADA services
  7. Verify the installation and functionality
Caveat Review release notes for any configuration or compatibility changes between your current version and 5.8.4

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

Fix this in Rapid Scada Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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