CVE-2022-46141
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 STEP 7 (TIA Portal) (All versions < V19). An information disclosure vulnerability could allow a local attacker to gain access to the access level password of the SIMATIC S7-1200 and S7-1500 CPUs, when entered by a legitimate user in the hardware configuration of the affected application.
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 confidenceA local information disclosure vulnerability in SIMATIC STEP 7 (TIA Portal) versions prior to V19 allows a local attacker to retrieve access level passwords entered by legitimate users when configuring hardware for SIMATIC S7-1200 and S7-1500 CPUs. The passwords are stored or handled insecurely in the application, exposing credentials that control access to industrial PLCs.
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< 19CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Locate the installed TIA Portal versionOpen SIMATIC STEP 7 (TIA Portal) and navigate to Help > About, or check Windows Programs and Features for Siemens SIMATIC STEP 7 Professional/Advanced entry which displays the version numberAffected if The displayed version is earlier than V19 (for example V17, V18, or any version number less than 19)
-
Confirm the full version numberIn Programs and Features, locate the SIMATIC STEP 7 entry and note the full version string (such as V17 Update 4 or V18 Update 2)Affected if The version string does not begin with 19 or higher (versions prior to V19 are affected)
-
Check for TIA Portal Openness if installedIf TIA Portal Openness (automation software interface) is installed, it may store configuration files; review any project files for stored CPU access credentials in plaintextAffected if Project files contain unprotected passwords for S7-1200 or S7-1500 CPU access levels
You are affected if SIMATIC STEP 7 (TIA Portal) installed on this system is any version prior to V19, as earlier versions store CPU access passwords insecurely when configuring S7-1200 and S7-1500 hardware.
Generated from the published advisory. Verify against your own configuration.
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 · scoped19
Update SIMATIC STEP 7 (TIA Portal) to version V19 or later to remediate this vulnerability. Review and rotate any exposed S7 CPU access passwords as a precautionary measure.
SIMATIC STEP 7 (TIA Portal) V19
- 1. Back up all existing STEP 7 (TIA Portal) projects before making any changes
- 2. Download SIMATIC STEP 7 (TIA Portal) V19 or later from Siemens industry online support or your existing Siemens distribution channel
- 3. Uninstall the current version of SIMATIC STEP 7 (TIA Portal) if upgrading from a significantly older version, or use the update mechanism if upgrading from a recent version
- 4. Install STEP 7 (TIA Portal) V19 or later following the installation wizard prompts
- 5. After installation, verify the version by opening TIA Portal and checking the version information (Help > About TIA Portal)
- 6. Re-open existing projects and re-enter CPU access level passwords in the hardware configuration if prompted, as the stored credentials may need to be re-confirmed in the corrected application
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-46141 — 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-46141 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