dbcve.org
Simatic Cp 1242 7 V2 FirmwareOperating system · Siemens

CVE-2022-34819

CRITICAL · 10.0 CVSS v3.1 Published 2022-07-12
Fix available
A fix is available. Upgrade to 3.0.22 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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 CP 1242-7 V2 (All versions < V3.3.46), SIMATIC CP 1243-1 (All versions < V3.3.46), SIMATIC CP 1243-7 LTE EU (All versions < V3.3.46), SIMATIC CP 1243-7 LTE US (All versions < V3.3.46), SIMATIC CP 1243-8 IRC (All versions < V3.3.46), SIMATIC CP 1542SP-1 IRC (All versions >= V2.0 < V2.2.28), SIMATIC CP 1543-1 (All versions < V3.0.22), SIMATIC CP 1543SP-1 (All versions >= V2.0 < V2.2.28), SIPLUS ET 200SP CP 1542SP-1 IRC TX RAIL (All versions >= V2.0 < V2.2.28), SIPLUS ET 200SP CP 1543SP-1 ISEC (All versions >= V2.0 < V2.2.28), SIPLUS ET 200SP CP 1543SP-1 ISEC TX RAIL (All versions >= V2.0 < V2.2.28), SIPLUS NET CP 1242-7 V2 (All versions < V3.3.46), SIPLUS NET CP 1543-1 (All versions < V3.0.22), SIPLUS S7-1200 CP 1243-1 (All versions < V3.3.46), SIPLUS S7-1200 CP 1243-1 RAIL (All versions < V3.3.46). The application lacks proper validation of user-supplied data when parsing specific messages. This could result in a heap-based buffer overflow. An attacker could leverage this vulnerability to execute code in the context of device.

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

Heap-based buffer overflow vulnerability in SIMATIC CP communication processors due to lack of proper validation of user-supplied data when parsing specific messages. An attacker can achieve remote code execution in the context of the device. Affected devices include CP 1242-7 V2, CP 1243-1, CP 1243-7 LTE, CP 1542SP-1 IRC, CP 1543-1, and related SIPLUS variants.

MitigationUpdate firmware to patched versions (V3.3.46, V2.2.28, or V3.0.22 depending on device model) or apply compensating controls such as network segmentation and access controls to limit exposure to untrusted networks.

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 Cp 1242 7 V2 FirmwareOperating system
Affected:all versions
Simatic Cp 1243 1 FirmwareOperating system
Affected:all versions
Simatic Cp 1243 7 Lte Eu FirmwareOperating system
Affected:all versions
Simatic Cp 1243 7 Lte Us FirmwareOperating system
Affected:all versions
Simatic Cp 1243 8 Irc FirmwareOperating system
Affected:all versions
Simatic Cp 1542sp 1 Irc FirmwareOperating system
Affected:>= 2.0
Simatic Cp 1543 1 FirmwareOperating system
Affected:< 3.0.22
Simatic Cp 1543sp 1 FirmwareOperating system
Affected:>= 2.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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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
    Locate the SIMATIC CP communication processor on the network or physical device. Check the model number label or query the device via its management interface for the exact model designation (e.g., CP 1242-7 V2, CP 1243-1, CP 1543-1).
    Affected if The device model matches one of the affected models: CP 1242-7 V2, CP 1243-1, CP 1243-7 LTE (EU/US), CP 1243-8 IRC, CP 1542SP-1 IRC, CP 1543-1, or CP 1543SP-1 (or their SIPLUS variants).
  2. Retrieve the installed firmware version
    Access the device web interface, TIA Portal project, or use SNMP/syslog to query the firmware version. Compare the version number against the affected ranges provided.
    Affected if The firmware version is: all versions for CP 1242-7 V2, CP 1243-1, CP 1243-7 LTE (EU/US), CP 1243-8 IRC; >= 2.0 for CP 1542SP-1 IRC and CP 1543SP-1; or < 3.0.22 for CP 1543-1.
  3. Verify network exposure of the CP device
    Review network segmentation and firewall rules to determine if the CP device management or communication ports are reachable from untrusted networks or the internet.
    Affected if The device is directly accessible from untrusted networks without compensating controls such as VLAN segmentation or firewall filtering.
  4. Check for anomalous network traffic
    Monitor network logs or IDS/IPS alerts for unusual or malformed packets targeting the CP device communication ports, as the vulnerability is triggered by parsing specific malicious messages.
    Affected if Unexpected or malformed traffic directed at the device is observed, indicating potential exploitation attempts.

A user is affected if they have a matching CP device model with a firmware version within the affected ranges AND the device is exposed to network attacks.

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.0.22 or later
Fixed in 3.0.22
Vendor patch cert-portal.siemens.com →
Interim mitigation

Update firmware to patched versions (V3.3.46, V2.2.28, or V3.0.22 depending on device model) or apply compensating controls such as network segmentation and access controls to limit exposure to untrusted networks.

Recommended fix High confidence

V3.3.46 for CP 1242-7 V2/1243-1/1243-7 LTE EU/1243-7 LTE US/1243-8 IRC; V2.2.28 for CP 1542SP-1 IRC/1543SP-1; V3.0.22 for CP 1543-1

  1. Identify the exact model and current firmware version of the affected SIMATIC CP device using the device's web interface or TIA Administration console
  2. Download the appropriate firmware update from Siemens Industry Online Support (support.industry.siemens.com) or the vendor patch document
  3. Review the firmware release notes to understand any configuration or compatibility considerations
  4. Back up the current device configuration using TIA Portal or the device's backup/restore functionality
  5. Establish a maintenance window as firmware updates may cause brief network disruption
  6. Upload and install the new firmware via the device's web interface, TIA Portal, or appropriate update mechanism
  7. After update, verify the firmware version matches the target fixed version (V3.3.46 for CP 1242-7 V2/1243-x series; V2.2.28 for CP 1542SP-1 IRC/1543SP-1; V3.0.22 for CP 1543-1)
  8. Restore the device configuration from backup if necessary
Caveat Firmware updates may temporarily disrupt communications; ensure proper change management and maintenance window is scheduled; review release notes for any configuration changes required

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

Fix this in Simatic Cp 1242 7 V2 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
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,240.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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