CVE-2022-1989
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 · uneditedAll CODESYS Visualization versions before V4.2.0.0 generate a login dialog vulnerable to information exposure allowing a remote, unauthenticated attacker to enumerate valid users.
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 · moderate confidenceThe login dialog in CODESYS Visualization versions before V4.2.0.0 reveals different responses for valid versus invalid usernames, allowing remote unauthenticated attackers to enumerate valid user accounts through repeated login attempts.
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>= 4.0.0.0, < 4.2.0.0CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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.
-
Check if CODESYS Visualization is installedOn Windows, open Programs and Features or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion' in PowerShell to list installed programs. Look for 'CODESYS Visualization' in the results.Affected if CODESYS Visualization is not found in the installed programs list, meaning the product is not installed.
-
Identify the installed version of CODESYS VisualizationIf found, note the exact version number displayed (DisplayVersion field). The vulnerable versions start at 4.0.0.0 and include any version up to but not including 4.2.0.0.Affected if The installed version matches the pattern 4.0.x.x or 4.1.x.x, indicating it falls within the range >= 4.0.0.0 and < 4.2.0.0.
-
Verify the login dialog is accessibleAttempt to access the CODESYS Visualization login interface through the application or web interface if web visualization is enabled. This vulnerability is exploitable remotely by unauthenticated attackers making login requests.Affected if The login dialog is exposed and accepts authentication attempts, allowing repeated probes to distinguish between valid and invalid usernames based on response differences.
-
Confirm version is within vulnerable rangeCompare the installed version number against the affected range: versions 4.0.0.0 through 4.1.x.x are vulnerable. Versions 4.2.0.0 and later are patched.Affected if The version is less than 4.2.0.0 (e.g., 4.0.0.0, 4.0.1.0, 4.1.0.0, 4.1.1.0), placing it within the vulnerable range.
A user is affected if CODESYS Visualization version 4.0.0.0 or higher but lower than 4.2.0.0 is installed and its login dialog is accessible for authentication attempts.
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 · scoped4.2.0.0
Update CODESYS Visualization to version V4.2.0.0 or later to obtain the patched login dialog that does not expose user enumeration information.
CODESYS Visualization V4.2.0.0 or later
- Obtain CODESYS Visualization V4.2.0.0 or later from the official CODESYS download portal (customers.codesys.com)
- Review CODESYS upgrade documentation and release notes for V4.2.0.0
- Create a backup of the current visualization project and configuration
- Test the upgrade in a non-production environment before deploying
- Apply the upgrade to the production CODESYS Visualization installation following standard CODESYS update procedures
- Verify that the login dialog no longer exposes user enumeration information
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-1989 — 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-1989 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