dbcve.org
6gk5205 3bb00 2ab2 FirmwareOperating system · Siemens

CVE-2023-44374

HIGH · 8.8 CVSS v3.1 Published 2023-11-14
Fix available
A fix is available. Upgrade to 4.5 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 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 (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), SCALANCE WAB762-1 (6GK5762-1AJ00-6AA0) (All versions < V3.0.0), SCALANCE WAM763-1 (6GK5763-1AL00-7DA0) (All versions < V3.0.0), SCALANCE WAM763-1 (ME) (6GK5763-1AL00-7DC0) (All versions < V3.0.0), SCALANCE WAM763-1 (US) (6GK5763-1AL00-7DB0) (All versions < V3.0.0), SCALANCE WAM766-1 (6GK5766-1GE00-7DA0) (All versions < V3.0.0), SCALANCE WAM766-1 (ME) (6GK5766-1GE00-7DC0) (All versions < V3.0.0), SCALANCE WAM766-1 (US) (6GK5766-1GE00-7DB0) (All versions < V3.0.0), SCALANCE WAM766-1 EEC (6GK5766-1GE00-7TA0) (All versions < V3.0.0), SCALANCE WAM766-1 EEC (ME) (6GK5766-1GE00-7TC0) (All versions < V3.0.0), SCALANCE WAM766-1 EEC (US) (6GK5766-1GE00-7TB0) (All versions < V3.0.0), SCALANCE WUB762-1 (6GK5762-1AJ00-1AA0) (All versions < V3.0.0), SCALANCE WUB762-1 iFeatures (6GK5762-1AJ00-2AA0) (All versions < V3.0.0), SCALANCE WUM763-1 (6GK5763-1AL00-3AA0) (All versions < V3.0.0), SCALANCE WUM763-1 (6GK5763-1AL00-3DA0) (All versions < V3.0.0), SCALANCE WUM763-1 (US) (6GK5763-1AL00-3AB0) (All versions < V3.0.0), SCALANCE WUM763-1 (US) (6GK5763-1AL00-3DB0) (All versions < V3.0.0), SCALANCE WUM766-1 (6GK5766-1GE00-3DA0) (All versions < V3.0.0), SCALANCE WUM766-1 (ME) (6GK5766-1GE00-3DC0) (All versions < V3.0.0), SCALANCE WUM766-1 (USA) (6GK5766-1GE00-3DB0) (All versions < V3.0.0). Affected devices allow to change the password, but insufficiently check which password is to be changed. With this an authenticated attacker could, under certain conditions, be able to change the password of another, potential admin user, which could allow to escalate privileges.

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 improper access control flaw in the password change functionality of affected Siemens RUGGEDCOM and SCALANCE devices. The mechanism insufficiently validates which user's password is being changed, allowing an authenticated attacker to modify the password of another user, potentially an administrator, leading to privilege escalation.

MitigationUpdate firmware to V8.0 (or V3.0.0 for wireless WAB/WAM/WUB/WUM models) as specified in the official Siemens advisory. If updating is not immediately feasible, restrict administrative access to trusted personnel only and monitor for unauthorized password change attempts.

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
6gk5205 3bb00 2ab2 FirmwareOperating system
Affected:< 4.5
6gk5205 3bb00 2tb2 FirmwareOperating system
Affected:< 4.5
6gk5205 3bd00 2tb2 FirmwareOperating system
Affected:< 4.5
6gk5205 3bd00 2ab2 FirmwareOperating system
Affected:< 4.5
6gk5205 3bf00 2tb2 FirmwareOperating system
Affected:<= 4.5
6gk5205 3bf00 2ab2 FirmwareOperating system
Affected:< 4.5
6gk5208 0ba00 2tb2 FirmwareOperating system
Affected:< 4.5
6gk5208 0ba00 2ab2 FirmwareOperating system
Affected:< 4.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
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. Identify device model
    Check the device model number on the physical device or in the web interface/system info. Look for model numbers: 6gk5205-3bb00-2ab2, 6gk5205-3bb00-2tb2, 6gk5205-3bd00-2tb2, 6gk5205-3bd00-2ab2, 6gk5205-3bf00-2tb2, 6gk5205-3bf00-2ab2, 6gk5208-0ba00-2tb2, or 6gk5208-0ba00-2ab2.
    Affected if The device model matches any of the listed affected models.
  2. Check firmware version
    Access the device web interface or CLI and navigate to System Information or Firmware Version. For most models, compare the version to 4.5 (note: model 6gk5205-3bf00-2tb2 is affected at <=4.5, others at <4.5).
    Affected if Firmware version is less than 4.5 (or less than or equal to 4.5 for the 6gk5205-3bf00-2tb2 model).
  3. Verify password change functionality is accessible
    Confirm the device web interface or management console is reachable and the password change functionality is exposed. This is typically found under User Management, Users, or Account Settings in the web interface.
    Affected if The device management interface with password change capability is accessible on the network.

The device is affected if it is one of the listed models (6gk5205 or 6gk5208 variants) AND its firmware version is below 4.5 (or at or below 4.5 for the 6gk5205-3bf00-2tb2), and the management interface is accessible.

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

Update firmware to V8.0 (or V3.0.0 for wireless WAB/WAM/WUB/WUM models) as specified in the official Siemens advisory. If updating is not immediately feasible, restrict administrative access to trusted personnel only and monitor for unauthorized password change attempts.

Recommended fix High confidence

V8.0 (or V3.0.0 for wireless access point models)

  1. Identify the specific SCALANCE or RUGGEDCOM device model from the list of affected products
  2. Determine the current firmware version by accessing the device's web interface or using Siemens' management tools
  3. For SCALANCE M804PB, M812-1, M816-1, M826-2, M874-2, M874-3, M876-3, M876-4, MUM853-1, MUM856-1, S615 devices: Upgrade firmware to version V8.0 or later
  4. For SCALANCE WAB762-1, WAM763-1, WAM766-1, WUB762-1, WUM763-1, WUM766-1 devices: Upgrade firmware to version V3.0.0 or later
  5. For RUGGEDCOM RM1224 LTE (4G) devices: Upgrade firmware to version V8.0 or later
  6. After upgrade, verify the firmware version and test device functionality
  7. Review user accounts and reset any potentially compromised passwords
Caveat Review Siemens release notes for V8.0/V3.0.0 to check 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 6gk5205 3bb00 2ab2 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
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,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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