dbcve.org
Command InjectionWeakness · CWE-77

CVE-2024-30213

HIGH · 8.8 CVSS v3.1 Published 2024-07-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
StoneFly Storage Concentrator (SC and SCVM) before 8.0.4.26 allows remote authenticated users to achieve Command Injection via a Ping URL, leading to 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

StoneFly Storage Concentrator versions before 8.0.4.26 contain a command injection vulnerability in the Ping functionality. Remote authenticated users can inject arbitrary OS commands through the Ping URL parameter, achieving unauthenticated remote code execution on the underlying system.

MitigationUpgrade StoneFly Storage Concentrator (SC and SCVM) to version 8.0.4.26 or later to patch the command injection vulnerability in the Ping feature. If immediate patching is not possible, restrict network access to the management interface to trusted IP addresses and audit existing administrator accounts.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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. Identify StoneFly Storage Concentrator deployment
    Locate any StoneFly Storage Concentrator (SC or SCVM) appliances in your environment through asset inventory, network scans, or documentation
    Affected if StoneFly Storage Concentrator software is present in the environment
  2. Determine installed version
    Access the management interface or use system commands to retrieve the StoneFly Storage Concentrator version number. Compare it against the fixed version 8.0.4.26
    Affected if Installed version is earlier than 8.0.4.26
  3. Verify Ping feature accessibility
    Confirm whether the Ping functionality is enabled and accessible on the management interface. Check if the web UI or API endpoint for Ping is reachable
    Affected if The Ping feature is enabled and exposed
  4. Assess management interface network exposure
    Review network firewall rules, access control lists, or VPN configurations to determine if the StoneFly management interface is accessible from untrusted networks
    Affected if The management interface is reachable from untrusted or public networks
  5. Check for indicators of compromise
    Review web server logs, audit logs, and system logs for suspicious Ping requests containing shell metacharacters (such as ;, |, &&, or backticks) or unexpected command executions
    Affected if Logs show anomalous Ping requests or unauthorized command execution

You are affected if StoneFly Storage Concentrator versions before 8.0.4.26 are deployed with the Ping feature accessible, especially if the management interface is network-exposed.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade StoneFly Storage Concentrator (SC and SCVM) to version 8.0.4.26 or later to patch the command injection vulnerability in the Ping feature. If immediate patching is not possible, restrict network access to the management interface to trusted IP addresses and audit existing administrator accounts.

Recommended fix High confidence

8.0.4.26 or later

  1. 1. Access the StoneFly Storage Concentrator administrative interface
  2. 2. Navigate to the system settings or firmware management section
  3. 3. Identify the current firmware version (confirm it is below 8.0.4.26)
  4. 4. Obtain the firmware version 8.0.4.26 or later from the official StoneFly support portal or vendor
  5. 5. Follow StoneFly's standard firmware upgrade procedure to apply version 8.0.4.26
  6. 6. After upgrade, verify the new version is installed and confirm the vulnerability is resolved

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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