dbcve.org
Ruggedcom CrossbowApplication · Siemens

CVE-2023-37372

CRITICAL · 9.8 CVSS v3.1 Published 2023-08-08
Fix available
A fix is available. Upgrade to 5.4 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.4). The affected applications is vulnerable to SQL injection. This could allow an unauthenticated remote attackers to execute arbitrary SQL queries on the server database.

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

SQL injection vulnerability in RUGGEDCOM CROSSBOW allows unauthenticated remote attackers to execute arbitrary SQL queries on the server database due to insufficient input validation in affected applications (versions < V5.4). The critical CVSS 9.8 score reflects the combination of network-exploitable, low-privilege-required SQL injection with potential complete database compromise.

MitigationUpgrade RUGGEDCOM CROSSBOW to version V5.4 or later to receive the vendor patch. As an interim control, restrict network access to the affected system and deploy a WAF to filter malicious SQL payloads.

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.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
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 installation
    Identify whether RUGGEDCOM CROSSBOW software is installed on the system by reviewing installed applications, program directories, or system inventory records
    Affected if RUGGEDCOM CROSSBOW is present on the system
  2. Check installed version
    Locate the installed version of RUGGEDCOM CROSSBOW through the application GUI, system information panel, or version documentation file
    Affected if The version is identified as anything below V5.4 (such as V5.3, V5.2, or earlier releases)
  3. Assess network exposure
    Determine if the RUGGEDCOM CROSSBOW web interface or management ports are accessible from untrusted network segments by reviewing firewall rules and network configurations
    Affected if The application web interface is reachable from external or untrusted networks without proper access controls
  4. Review web application logs
    Examine application and web server logs for unusual SQL syntax, database error messages, or patterns indicative of SQL injection attempts
    Affected if Logs contain SQL errors, suspicious SQL-like queries in request parameters, or evidence of injection payloads
  5. Check for unauthorized database access indicators
    Review database logs or audit records for unexpected queries, unauthorized table access, or modifications to sensitive tables
    Affected if Database contains unexpected queries, new tables, or modifications to user/authentication tables from unauthorized sources

The environment is affected if RUGGEDCOM CROSSBOW versions prior to V5.4 are installed and the web interface is network-accessible, as the unauthenticated SQL injection can be exploited remotely.

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.4 or later
Fixed in 5.4
Interim mitigation

Upgrade RUGGEDCOM CROSSBOW to version V5.4 or later to receive the vendor patch. As an interim control, restrict network access to the affected system and deploy a WAF to filter malicious SQL payloads.

Recommended fix High confidence

V5.4

  1. Backup the current Ruggedcom Crossbow configuration before starting the upgrade process
  2. Download the V5.4 release of Ruggedcom Crossbow from the official Siemens cert-portal or Siemens support channels
  3. Review Siemens upgrade documentation for Ruggedcom Crossbow specific to your deployment
  4. Execute the upgrade process according to Siemens official upgrade procedures
  5. After upgrade, verify the version shows V5.4 or higher
  6. Confirm the SQL injection vulnerability is remediated by validating the application functions correctly
Caveat Review Siemens release notes for V5.4 to check for any configuration or functionality changes that may affect your deployment

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
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,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 $12,352.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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