dbcve.org
Ruggedcom CrossbowApplication · Siemens

CVE-2024-27939

CRITICAL · 9.8 CVSS v3.1 Published 2024-05-14
Fix available
A fix is available. Upgrade to 5.5 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
A vulnerability has been identified in RUGGEDCOM CROSSBOW (All versions < V5.5). The affected systems allow the upload of arbitrary files of any unauthenticated user. An attacker could leverage this vulnerability and achieve arbitrary code execution with system privileges.

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

RUGGEDCOM CROSSBOW versions before V5.5 contain an unauthenticated arbitrary file upload vulnerability. An unauthenticated attacker can upload any files to the system, which can be leveraged to achieve arbitrary code execution with system privileges.

MitigationUpgrade RUGGEDCOM CROSSBOW to version V5.5 or later to remediate this 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
Ruggedcom CrossbowApplication
Affected:< 5.5

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. Confirm RUGGEDCOM CROSSbow is present
    Identify if the RUGGEDCOM CROSSbow software or service is installed on the system. This may be visible as a running service, a web application on a specific port, or installed software packages. Check for processes named 'crossbow' or services listening on expected management ports.
    Affected if The product is present on the system
  2. Determine installed version
    Locate the installed version of RUGGEDCOM CROSSbow. Common methods include: (1) Checking the web management interface for a version display, (2) Using CLI commands if accessible (such as 'show version' or 'crossbow -v'), (3) Examining installation directories for version files, or (4) Querying the service/API if exposed.
    Affected if The version cannot be determined or is found to be before V5.5
  3. Compare version against affected range
    Verify the installed version against the affected range. Any version lower than V5.5 is vulnerable. Common version formats may include V5.4.x, V5.3.x, or earlier releases.
    Affected if The installed version is < V5.5 (e.g., V5.4.1, V5.3, V5.2)
  4. Check for unauthenticated access exposure
    Assess whether the file upload functionality is network-accessible without authentication. This vulnerability allows unauthenticated file upload, meaning no login should be required to access upload endpoints. Verify if the management interface is exposed to untrusted networks.
    Affected if The management interface is accessible without authentication and the version is < V5.5

The environment is affected if RUGGEDCOM CROSSbow is installed and the version is identified as anything before V5.5.

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 5.5 or later
Fixed in 5.5
Interim mitigation

Upgrade RUGGEDCOM CROSSBOW to version V5.5 or later to remediate this vulnerability.

Recommended fix Moderate confidence

V5.5

  1. Obtain Ruggedcom Crossbow V5.5 or later from the official Siemens cert-portal or support website
  2. Review the V5.5 release notes and upgrade documentation for any specific requirements
  3. Backup the current system configuration before initiating the upgrade
  4. Follow Siemens official upgrade procedure to install V5.5
  5. Verify the upgrade was successful and confirm the arbitrary file upload vulnerability is no longer present
Caveat Review V5.5 release notes for any configuration changes or compatibility considerations before upgrading

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

Fix this in Ruggedcom Crossbow Scoped from the published advisory
  • Consultation8.0 h
  • Implementation12.0 h
  • Testing16.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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