dbcve.org
Ruggedcom CrossbowApplication · Siemens

CVE-2024-27947

MEDIUM · 5.3 CVSS v3.1 Published 2024-05-14
Fix available
A fix is available. Upgrade to 5.5 or later.
See remediation →
62/100
Remediation priority · Elevated
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 could allow log messages to be forwarded to a specific client under certain circumstances. An attacker could leverage this vulnerability to forward log messages to a specific compromised client.

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

RUGGEDCOM CROSSBOW versions prior to V5.5 contain a vulnerability that allows log messages to be forwarded to a specific client under certain conditions. An attacker who can influence or control the destination client could potentially intercept log data that may contain system information, events, or diagnostic data.

MitigationUpgrade to RUGGEDCOM CROSSBOW V5.5 or later. Until upgraded, restrict network access to log forwarding ports and monitor for unauthorized log redirection.

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
Low
Integrity
None
Availability
None

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

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 RUGGEDCOM CROSSBOW version
    Access the device management interface or use the system information command provided by RUGGEDCOM CROSSBOW to retrieve the current software version
    Affected if The installed version is earlier than V5.5 (e.g., V5.4, V5.3, etc.)
  2. Verify if log forwarding is enabled
    Inspect the log forwarding configuration settings within the RUGGEDCOM CROSSBOW management interface or configuration files
    Affected if Log forwarding is actively enabled on the device
  3. Review configured log forwarding destinations
    Examine the list of configured log destination clients in the log forwarding settings
    Affected if There are log forwarding destinations configured, especially any that are untrusted, unknown, or accessible to unauthorized parties on the network
  4. Inspect network exposure of log forwarding ports
    Check which network ports are open and accessible related to log forwarding, and verify if they are exposed to untrusted networks
    Affected if Log forwarding ports are accessible from untrusted or external network segments

A user is affected if RUGGEDCOM CROSSBOW version is below V5.5 AND log forwarding is enabled with accessible destination clients that could be influenced by an attacker

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 to RUGGEDCOM CROSSBOW V5.5 or later. Until upgraded, restrict network access to log forwarding ports and monitor for unauthorized log redirection.

Recommended fix Moderate confidence

Ruggedcom Crossbow V5.5

  1. 1. Obtain Ruggedcom Crossbow V5.5 firmware from Siemens official support portal (cert-portal.siemens.com or siemens.com/support)
  2. 2. Review the V5.5 release notes to understand changes and any migration requirements
  3. 3. Back up the current Ruggedcom Crossbow configuration before proceeding with the upgrade
  4. 4. Upload the V5.5 firmware file to the Ruggedcom Crossbow device following Siemens upgrade procedures
  5. 5. Apply the firmware update to the device
  6. 6. After upgrade completes, verify the device is running V5.5 and confirm normal operation
  7. 7. Verify that log forwarding functionality is working as expected with proper access controls configured
Caveat Industrial firmware upgrades may require downtime and should be tested in a non-production environment first; review Siemens migration guides for compatibility notes

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

Fix this in Ruggedcom Crossbow Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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