CVE-2022-34820
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 · uneditedA 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 does not correctly escape some user provided fields during the authentication process. This could allow an attacker to inject custom commands and execute arbitrary code with elevated 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 analysisUser input reaches a command interpreter without being fully separated from the command itself, so an attacker can append instructions of their own. Because those run with the application's privileges, it frequently means control of the host. The lasting fix is to avoid constructing commands from input — call APIs directly and pass arguments as data, never as concatenated strings.
General guidance for the command injection class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →
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< 3.3.46< 3.3.46< 3.3.46< 3.3.46< 3.3.46>= 2.0, < 2.2.28< 3.0.22>= 2.0, < 2.2.28CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
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 · scoped2.2.283.0.223.3.46
Upgrade to firmware version 3.3.46 for CP 1242-7 V2, CP 1243-1, CP 1243-7 LTE EU/US, CP 1243-8 IRC; upgrade to firmware version 2.2.28 for CP 1542SP-1 IRC and CP 1543SP-1; upgrade to firmware version 3.0.22 for CP 1543-1
- 1. Identify the exact model and current firmware version of the SIMATIC CP device by accessing the device's web interface or using TIA Portal.
- 2. Download the corresponding firmware update from Siemens Industry Online Support (https://support.industry.siemens.com/): for CP 1242-7 V2, CP 1243-1, CP 1243-7 LTE EU/US, and CP 1243-8 IRC, download firmware version 3.3.46 or later; for CP 1542SP-1 IRC and CP 1543SP-1, download firmware version 2.2.28 or later; for CP 1543-1, download firmware version 3.0.22 or later.
- 3. Create a full backup of the current device configuration using TIA Portal or the device's built-in backup function.
- 4. Establish a direct Ethernet connection to the CP device (bypass any intermediate networks) to perform the firmware update.
- 5. Upload the new firmware file through the device's web interface under 'Firmware Update' or via TIA Portal's 'Online & Diagnostics' function.
- 6. After the firmware update completes, verify the device reports the new version number (3.3.46, 2.2.28, or 3.0.22 as applicable).
- 7. Restore the device configuration from the backup created in step 3.
- 8. Verify normal operation and test that the authentication functionality works correctly.
Generated from the published advisory — verify against the referenced sources before acting.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-34820 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-34820 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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