Rapid ScadaApplication · Rapidscada

CVE-2024-21794

MEDIUM · 5.4 CVSS v3.1 Published 2024-02-02
Fix available
A fix is available. Upgrade to after 5.8.4 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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, an attacker can redirect users to malicious pages through the login page.

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

This is an open redirect vulnerability in Rapid SCADA versions prior to 5.8.4. Attackers can craft malicious URLs through the login page parameter to redirect users to external malicious websites after authentication attempts.

MitigationUpgrade Rapid SCADA to Version 5.8.4 or later to obtain the security patch for this open redirect vulnerability.

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
Low
User interaction
Required
Scope
Changed
Confidentiality
None
Integrity
Low
Availability
Low

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

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
    Check the version information through the application's About page, installation directory, or Windows Programs and Features. Common locations include the application's config files or the main executable's properties.
    Affected if The installed version is 5.8.4 or lower, or if the version cannot be confirmed as 5.8.5 or higher
  2. Verify login page accessibility
    Access the Rapid SCADA web interface login page (typically at /Login or the root URL of the installation) using a web browser or command-line tool like curl.
    Affected if The login page is publicly or internally accessible without additional authentication
  3. Test for open redirect parameter
    Submit a login attempt with a crafted returnUrl parameter pointing to an external domain (for example: /Login?returnUrl=//attacker.com). Observe whether the application redirects to the specified external site after the login attempt.
    Affected if The application redirects to the external URL specified in the parameter rather than rejecting it or only allowing internal paths
  4. Review login page parameter configuration
    Inspect the login page's source code or configuration files to identify how the returnUrl or redirect parameter is handled and validated.
    Affected if The parameter accepts absolute URLs to external domains without validation or restriction

A user is affected if Rapid SCADA version 5.8.4 or lower is installed and the login page accepts and processes unvalidated redirect parameters to external URLs.

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 Rapid SCADA to Version 5.8.4 or later to obtain the security patch for this open redirect vulnerability.

Recommended fix High confidence

Version 5.8.4

  1. Back up the current Rapid SCADA installation and database before proceeding
  2. Download Rapid SCADA version 5.8.4 or later from the official source at rapidscada.org
  3. Stop the Rapid SCADA service
  4. Install the updated version following the standard upgrade procedure
  5. Start the Rapid SCADA service and verify the login page functions correctly

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

Fix this in Rapid Scada Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-21794 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