dbcve.org
Rapid ScadaApplication · Rapidscada

CVE-2024-21852

HIGH · 8.8 CVSS v3.1 Published 2024-02-01
Fix available
A fix is available. Upgrade to after 5.8.4 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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, an attacker can supply a malicious configuration file by utilizing a Zip Slip vulnerability in the unpacking routine to achieve remote code execution.

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 contain a Zip Slip directory traversal vulnerability in the archive unpacking routine. An attacker can supply a malicious configuration file containing path traversal sequences (e.g., '../') to write files outside the intended extraction directory, potentially overwriting executable files or configuration scripts to achieve remote code execution.

MitigationUpgrade Rapid SCADA to version 5.8.4 or later, which contains the patched unpacking routine with proper path validation. Prior to deployment in production, validate the upgrade in a test environment to ensure SCADA functionality remains intact.

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 installed Rapid SCADA version
    Locate the Rapid SCADA installation directory and find the version information, typically in the application's main executable, configuration files, or installer logs. Common locations include the installation folder or Windows registry.
    Affected if The installed version is 5.8.4 or lower.
  2. Identify archive unpacking configuration
    Review the Rapid SCADA configuration to determine if the archive import or config file import functionality is enabled. Look for settings related to importing archives, configuration files, or packages that get automatically unpacked.
    Affected if Archive unpacking or config import features are active in the deployment.
  3. Examine config files for path traversal patterns
    Inspect any configuration files, archives, or import packages located in the Rapid SCADA data directories. Search for file contents or filenames containing '../' or '..\' sequences that could indicate exploitation attempts.
    Affected if Any config files or archives contain path traversal sequences or exist outside expected directories.
  4. Review extraction directories for unexpected files
    Check the directories where Rapid SCADA extracts archives or config files. Compare the actual extracted files against the expected set of files. Look for new or modified files in system directories, executable locations, or script folders.
    Affected if Files exist in directories outside the intended extraction path, or unexpected executables/scripts are present.

You are affected if Rapid SCADA version is 5.8.4 or lower AND the archive unpacking/config import feature is in use, with any evidence of path traversal in config files or unexpected files outside extraction directories.

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, which contains the patched unpacking routine with proper path validation. Prior to deployment in production, validate the upgrade in a test environment to ensure SCADA functionality remains intact.

Recommended fix High confidence

Version 5.8.4 or later

  1. Create a complete backup of the current Rapid SCADA installation including all configuration files, project data, and database
  2. Download Rapid SCADA Version 5.8.4 or later from the official rapidscada.org website
  3. Follow the official Rapid SCADA upgrade/installation instructions for your deployment type
  4. After upgrading, verify that the installation completed successfully by checking the application version
  5. Review configuration files to ensure they were properly migrated during the upgrade

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

Fix this in Rapid Scada Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,620
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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