Ruggedcom CrossbowApplication · Siemens

CVE-2023-27463

HIGH · 8.8 CVSS v3.1 Published 2023-03-14
Fix available
A fix is available. Upgrade to 5.3 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
A vulnerability has been identified in RUGGEDCOM CROSSBOW (All versions < V5.3). The audit log form of affected applications is vulnerable to SQL injection. This could allow authenticated 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's audit log form allows authenticated attackers to execute arbitrary SQL queries on the server database. The vulnerability exists in all versions prior to V5.3 and stems from improper input validation in SQL queries used by the audit log functionality.

MitigationUpgrade RUGGEDCOM CROSSBOW to version V5.3 or later. If immediate upgrade is not possible, implement input validation and parameterized queries on the audit log form as a compensating control.

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.3

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. Confirm RUGGEDCOM CROSSBOW installation
    Locate the RUGGEDCOM CROSSBOW installation and identify the installed version number, typically found in the product information page, system settings, or about dialog of the web management interface.
    Affected if The product is identified but shows a version lower than V5.3 (such as V5.2, V5.1, V4.x, etc.)
  2. Check audit log access
    Navigate to or attempt to access the audit log functionality within the RUGGEDCOM CROSSBOW web interface. Verify whether the audit log form is present and accessible.
    Affected if The audit log form is accessible without modification to the default configuration.
  3. Verify authentication status
    Determine if valid user credentials exist for the RUGGEDCOM CROSSBOW management interface. Check whether the user account used has privileges to access the audit log form.
    Affected if A valid authenticated session can be established with privileges to view the audit log form.

The environment is affected if RUGGEDCOM CROSSBOW is installed with a version prior to V5.3 and the audit log form is accessible to an authenticated user.

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.3 or later
Fixed in 5.3
Interim mitigation

Upgrade RUGGEDCOM CROSSBOW to version V5.3 or later. If immediate upgrade is not possible, implement input validation and parameterized queries on the audit log form as a compensating control.

Recommended fix High confidence

V5.3

  1. Identify the current installed version of Ruggedcom Crossbow
  2. Obtain Ruggedcom Crossbow V5.3 or later from Siemens official support channels (cert-portal.siemens.com or Siemens support)
  3. Review the upgrade documentation and release notes for any prerequisites or special instructions
  4. Schedule a maintenance window for the upgrade procedure
  5. Perform a complete backup of the current system configuration and database
  6. Follow the official Siemens upgrade procedure to install V5.3 or later
  7. Verify the upgrade was successful and confirm the SQL injection vulnerability is resolved
Caveat Review V5.3 release notes for any configuration or behavioral changes from previous versions

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

Fix this in Ruggedcom Crossbow Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-27463 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-27463 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