CVE-2022-1794
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 · uneditedThe CODESYS OPC DA Server prior V3.5.18.20 stores PLC passwords as plain text in its configuration file so that it is visible to all authorized Microsoft Windows users of the system.
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 confidenceThe CODESYS OPC DA Server versions prior to V3.5.18.20 store PLC passwords in plaintext within the server's configuration file. This file is readable by any authorized Windows user on the system, allowing unauthorized disclosure of credentials.
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>= 3.0.0, < 3.5.18.20CVSS 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.
-
Identify CODESYS OPC DA Server versionOpen the Windows Control Panel, go to Programs and Features, or use the application's About/Help menu to find the installed version of CODESYS OPC DA Server. Alternatively, check the version information in the installation directory or in the service properties if it runs as a Windows service.Affected if The installed version is 3.0.0 or higher but lower than 3.5.18.20
-
Locate the server configuration fileFind the configuration file used by CODESYS OPC DA Server. This is typically located in the installation directory or in a configuration folder under the CODESYS installation path. Look for files with extensions such as .cfg, .xml, .ini, or similar configuration formats.Affected if The configuration file exists and contains stored PLC password entries
-
Inspect stored credentialsOpen the configuration file using a text editor and search for entries that appear to contain passwords or credential data. Look for patterns such as password fields, credential settings, or PLC connection parameters that include password values.Affected if Password values are stored in plaintext (readable text) rather than being encrypted, hashed, or obfuscated
A system is affected if it runs CODESYS OPC DA Server version 3.0.0 or higher but below 3.5.18.20 AND has PLC passwords stored in plaintext within its configuration file.
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 · scoped3.5.18.20
Upgrade CODESYS OPC DA Server to version V3.5.18.20 or later, which implements proper password protection (encryption or hashing) in the configuration storage.
3.5.18.20 or later
- Upgrade CODESYS OPC DA Server to version 3.5.18.20 or later
- After upgrade, verify that PLC passwords are no longer stored in plain text in the configuration file
- If migrating an existing configuration, ensure new password storage mechanism is properly implemented
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-1794 — 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-1794 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