dbcve.org
6gk6108 4am00 2ba2 FirmwareOperating system · Siemens

CVE-2023-49691

MEDIUM · 6.7 CVSS v3.1 Published 2023-12-12
Fix available
A fix is available. Upgrade to 8.0 or later.
See remediation →
69/100
Remediation priority · Elevated
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 RM1224 LTE(4G) EU (6GK6108-4AM00-2BA2) (All versions < V8.0), RUGGEDCOM RM1224 LTE(4G) NAM (6GK6108-4AM00-2DA2) (All versions < V8.0), SCALANCE M804PB (6GK5804-0AP00-2AA2) (All versions < V8.0), SCALANCE M812-1 ADSL-Router (6GK5812-1AA00-2AA2) (All versions < V8.0), SCALANCE M812-1 ADSL-Router (6GK5812-1BA00-2AA2) (All versions < V8.0), SCALANCE M816-1 ADSL-Router (6GK5816-1AA00-2AA2) (All versions < V8.0), SCALANCE M816-1 ADSL-Router (6GK5816-1BA00-2AA2) (All versions < V8.0), SCALANCE M826-2 SHDSL-Router (6GK5826-2AB00-2AB2) (All versions < V8.0), SCALANCE M874-2 (6GK5874-2AA00-2AA2) (All versions < V8.0), SCALANCE M874-3 (6GK5874-3AA00-2AA2) (All versions < V8.0), SCALANCE M876-3 (6GK5876-3AA02-2BA2) (All versions < V8.0), SCALANCE M876-3 (ROK) (6GK5876-3AA02-2EA2) (All versions < V8.0), SCALANCE M876-4 (6GK5876-4AA10-2BA2) (All versions < V8.0), SCALANCE M876-4 (EU) (6GK5876-4AA00-2BA2) (All versions < V8.0), SCALANCE M876-4 (NAM) (6GK5876-4AA00-2DA2) (All versions < V8.0), SCALANCE MUM853-1 (EU) (6GK5853-2EA00-2DA1) (All versions < V8.0), SCALANCE MUM856-1 (EU) (6GK5856-2EA00-3DA1) (All versions < V8.0), SCALANCE MUM856-1 (RoW) (6GK5856-2EA00-3AA1) (All versions < V8.0), SCALANCE S615 EEC LAN-Router (6GK5615-0AA01-2AA2) (All versions < V8.0), SCALANCE S615 LAN-Router (6GK5615-0AA00-2AA2) (All versions < V8.0). An Improper Neutralization of Special Elements used in an OS Command with root privileges vulnerability exists in the handling of the DDNS configuration. This could allow malicious local administrators to issue commands on system level after a successful IP address update.

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

The vulnerability is an OS command injection flaw in the DDNS (Dynamic DNS) configuration handling of Siemens RUGGEDCOM RM1224 and SCALANCE industrial routers. Local administrators with malicious intent can execute arbitrary system-level commands with root privileges after a successful IP address update due to improper neutralization of special elements in the DDNS configuration process.

MitigationUpgrade all affected devices to firmware version V8.0 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
6gk6108 4am00 2ba2 FirmwareOperating system
Affected:< 8.0
6gk6108 4am00 2da2 FirmwareOperating system
Affected:< 8.0
6gk5804 0ap00 2aa2 FirmwareOperating system
Affected:< 8.0
6gk5812 1aa00 2aa2 FirmwareOperating system
Affected:< 8.0
6gk5812 1ba00 2aa2 FirmwareOperating system
Affected:< 8.0
6gk5816 1aa00 2aa2 FirmwareOperating system
Affected:< 8.0
6gk5816 1ba00 2aa2 FirmwareOperating system
Affected:< 8.0
6gk5826 2ab00 2ab2 FirmwareOperating system
Affected:< 8.0

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
Local
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/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 the device model
    Access the device web interface or CLI and locate the product model identifier (e.g., 6gk6108 4am00 2ba2, 6gk5812 1aa00 2aa2, etc.) in the device information or system status page
    Affected if The model number matches any of the affected variants: 6gk6108, 6gk5804, 6gk5812, 6gk5816, or 6gk5826
  2. Check the installed firmware version
    Access the device web interface under System > Firmware or use the CLI command 'show version' to retrieve the current firmware version
    Affected if The firmware version is below version 8.0 (for example, V7.x or earlier)
  3. Verify DDNS configuration status
    Access the device web interface under Network > DDNS or use the CLI to check if any DDNS provider is configured and enabled
    Affected if DDNS is configured and enabled on the device (the vulnerability is triggered during DDNS IP address updates)

The device is affected if it is one of the listed Siemens models running firmware below version 8.0 AND has DDNS feature configured and active.

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

Upgrade all affected devices to firmware version V8.0 or later to remediate this vulnerability.

Recommended fix High confidence

Firmware V8.0 or later

  1. 1. Identify the affected device model from the list of vulnerable products
  2. 2. Access the device's web interface or management console
  3. 3. Navigate to the firmware update or system maintenance section
  4. 4. Download the V8.0 firmware from Siemens official support portal (cert-portal.siemens.com) for your specific device model
  5. 5. Create a backup of the current device configuration before upgrading
  6. 6. Upload and apply the V8.0 firmware following Siemens upgrade instructions
  7. 7. After reboot, verify the firmware version shows V8.0 or later
  8. 8. Restore the configuration if needed and verify all services are operational
Caveat Review Siemens release notes for V8.0 for any configuration or feature changes that may affect your deployment

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

Fix this in 6gk6108 4am00 2ba2 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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