6gk5205 3bb00 2ab2 FirmwareOperating system · Siemens

CVE-2023-44321

MEDIUM · 6.5 CVSS v3.1 Published 2023-11-14
Fix available
A fix is available. Upgrade to 4.5 or later.
See remediation →
71/100
Remediation priority · Elevated
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
Affected devices do not properly validate the length of inputs when performing certain configuration changes in the web interface allowing an authenticated attacker to cause a denial of service condition. The device needs to be restarted for the web interface to become available again.

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 · moderate confidence

Affected devices fail to validate input length during certain configuration changes in the web interface. An authenticated attacker can submit oversized inputs that cause the web interface to crash, requiring a device restart to restore functionality.

MitigationRestrict administrative access to trusted users only. Implement and enforce proper input length validation on all configuration parameters in the web interface.

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 number
    Locate the product label on the physical SCALANCE device or access the device's web interface/system information page to confirm the exact model number (e.g., 6gk5205 3bb00 2ab2, 6gk5208 0ba00 2tb2)
    Affected if The model number matches one of the affected products listed in the CVE (any 6gk5205 or 6gk5208 variant with the specified suffixes)
  2. Check installed firmware version
    Access the device's web interface and navigate to System Information or Device Status to view the firmware version, or use the device's CLI command to query the firmware version (e.g., 'show version' or similar)
    Affected if The firmware version is below 4.5 (or 4.5 and below for the 6gk5205 3bf00 2tb2 model specifically)
  3. Verify web interface is enabled
    Check the device configuration to confirm the web interface (HTTP/HTTPS) service is enabled and accessible on the network
    Affected if The web interface is enabled and reachable on the network, making the input validation flaw accessible to an authenticated user

You are affected if your device is a SCALANCE X104-2 or X106-1 model (6gk5205/6gk5208 series) running firmware version below 4.5 with the web interface enabled and administrative authentication available.

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

Restrict administrative access to trusted users only. Implement and enforce proper input length validation on all configuration parameters in the web interface.

Recommended fix High confidence

Firmware version 4.5 or later for the affected 6gk5205 and 6gk5208 series devices

  1. 1. Identify the exact device model (e.g., 6gk5205 3bb00 2ab2) and confirm current firmware version via the device web interface or management console
  2. 2. Access the Siemens Industry Online Support portal (support.industry.siemens.com) or contact Siemens customer support to obtain the fixed firmware version 4.5 or later for your specific device model
  3. 3. Before upgrading, review Siemens upgrade documentation and ensure you have a backup of the current device configuration
  4. 4. Upload and install the fixed firmware version 4.5 or later following Siemens standard firmware update procedures for the affected device series
  5. 5. After the firmware upgrade completes, verify the device web interface is accessible and functioning normally
  6. 6. Restore the device configuration from backup if needed and confirm normal operation
Caveat Firmware upgrades on industrial devices may temporarily disrupt network connectivity; plan for maintenance window and follow Siemens upgrade documentation

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-44321 — 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-44321 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