dbcve.org
Simatic Mv540 H FirmwareOperating system · Siemens

CVE-2023-36521

HIGH · 7.5 CVSS v3.1 Published 2023-07-11
Fix available
A fix is available. Upgrade to 3.3.4 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 SIMATIC MV540 H (All versions < V3.3.4), SIMATIC MV540 S (All versions < V3.3.4), SIMATIC MV550 H (All versions < V3.3.4), SIMATIC MV550 S (All versions < V3.3.4), SIMATIC MV560 U (All versions < V3.3.4), SIMATIC MV560 X (All versions < V3.3.4). The result synchronization server of the affected products contains a vulnerability that may lead to a denial of service condition. An attacker may cause a denial of service situation of all socket-based communication of the affected products if the result server is enabled.

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

A denial of service vulnerability exists in the result synchronization server of SIMATIC MV540, MV550, and MV560 devices (all versions prior to V3.3.4). An attacker can cause DoS for all socket-based communication if the result server is enabled, potentially disrupting industrial barcode reader operations.

MitigationUpgrade to firmware version V3.3.4 or later; if the result server is not required, disable it 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
Simatic Mv540 H FirmwareOperating system
Affected:< 3.3.4
Simatic Mv540 S FirmwareOperating system
Affected:< 3.3.4
Simatic Mv550 H FirmwareOperating system
Affected:< 3.3.4
Simatic Mv550 S FirmwareOperating system
Affected:< 3.3.4
Simatic Mv560 U FirmwareOperating system
Affected:< 3.3.4
Simatic Mv560 X FirmwareOperating system
Affected:< 3.3.4

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

CVSS:3.1/AV:N/AC:L/PR:N/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 the SIMATIC MV model number
    Locate the device model label or check the device web interface or CLI for the exact model designation (MV540, MV550, or MV560).
    Affected if The model is not one of MV540, MV550, or MV560.
  2. Determine the installed firmware version
    Access the device web interface, CLI, or system information page and record the firmware version number.
    Affected if The firmware version is lower than V3.3.4.
  3. Verify if the result synchronization server is enabled
    Check the device configuration settings, network settings, or result server settings through the web interface or CLI.
    Affected if The result server feature is currently enabled.
  4. Confirm the result server is used for socket-based communication
    Review the result server configuration to determine if socket-based communication is configured for barcode reader operations.
    Affected if Socket-based communication is configured and active through the result server.

The device is affected if it is a SIMATIC MV540, MV550, or MV560 with firmware version prior to V3.3.4 AND the result synchronization server is enabled for socket-based communication.

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

Upgrade to firmware version V3.3.4 or later; if the result server is not required, disable it as a compensating control.

Recommended fix High confidence

Firmware V3.3.4

  1. Identify the specific Simatic MV model (H, S, U, or X variant) currently deployed
  2. Navigate to the device management interface or Siemens support portal to download firmware version 3.3.4 for the specific model
  3. Backup the current device configuration before initiating the firmware update
  4. Upload and install firmware version 3.3.4 following the standard Siemens firmware upgrade procedure for Simatic MV540/550/560 devices
  5. Verify that the firmware upgrade completed successfully and the device is operating normally
  6. Confirm that the result synchronization server functionality is restored and operating as expected after the upgrade

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

Fix this in Simatic Mv540 H Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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