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

CVE-2023-49692

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

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

This is a command injection vulnerability in the IPSEC configuration parsing functionality of Siemens industrial routers. The parsing code fails to properly neutralize special elements in user-supplied IPSEC configuration data, allowing a local administrator to inject and execute OS commands with root privileges.

MitigationApply Siemens firmware version V7.2.2 or later which contains the fix for proper input sanitization in the IPSEC configuration parser.

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:< 7.2.2
6gk6108 4am00 2da2 FirmwareOperating system
Affected:< 7.2.2
6gk5804 0ap00 2aa2 FirmwareOperating system
Affected:< 7.2.2
6gk5812 1aa00 2aa2 FirmwareOperating system
Affected:< 7.2.2
6gk5812 1ba00 2aa2 FirmwareOperating system
Affected:< 7.2.2
6gk5816 1aa00 2aa2 FirmwareOperating system
Affected:< 7.2.2
6gk5816 1ba00 2aa2 FirmwareOperating system
Affected:< 7.2.2
6gk5826 2ab00 2ab2 FirmwareOperating system
Affected:< 7.2.2

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 Siemens router model
    Locate the model number label on the physical device or check the device inventory/system information. Confirm it matches one of these affected models: 6gk6108 4am00 2ba2, 6gk6108 4am00 2da2, 6gk5804 0ap00 2aa2, 6gk5812 1aa00 2aa2, 6gk5812 1ba00 2aa2, 6gk5816 1aa00 2aa2, 6gk5816 1ba00 2aa2, or 6gk5826 2ab00 2ab2.
    Affected if The device model matches one of the listed product numbers.
  2. Determine the installed firmware version
    Access the router web interface or CLI and retrieve the current firmware version. This is typically found in the system status, device information, or firmware update section of the management interface.
    Affected if The installed firmware version is lower than 7.2.2.
  3. Verify IPSEC configuration access
    Check if the IPSEC configuration functionality is accessible. This vulnerability requires a local administrator to supply IPSEC configuration data. Determine whether you have administrative access to the IPSEC configuration panel in the router's management interface.
    Affected if You have local administrator access to configure IPSEC settings on the device.
  4. Confirm IPSEC is configured
    Review the IPSEC configuration settings on the router to determine whether any IPSEC tunnels or policies are actively configured.
    Affected if IPSEC tunnels or policies are configured on the device.

You are affected if your Siemens industrial router model matches one of the listed product numbers, your firmware version is below 7.2.2, and you have the ability to configure IPSEC settings as a local administrator.

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

Apply Siemens firmware version V7.2.2 or later which contains the fix for proper input sanitization in the IPSEC configuration parser.

Recommended fix High confidence

V7.2.2

  1. Identify the specific device model and current firmware version through the device web interface or CLI
  2. Backup the current device configuration to a secure location
  3. Download firmware version V7.2.2 or later from the Siemens Industry Online Support portal (https://support.industry.siemens.com/)
  4. Access the device administration interface and navigate to the firmware update section
  5. Upload and apply the V7.2.2 firmware file to the device
  6. After installation, restore the backed-up configuration if needed
  7. Reboot the device to complete the upgrade process
  8. Verify the firmware version is correctly reported as V7.2.2 or later in the device information
Caveat Review Siemens release notes for any configuration changes or feature modifications between your current version and V7.2.2

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
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
38.0 hours of engineering $6,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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