ZenonApplication · Abb

CVE-2022-34837

MEDIUM · 6.1 CVSS v3.1 Published 2022-08-24
Fix available
A fix is available. Upgrade to after 8.20 or later.
See remediation →
63/100
Remediation priority · Elevated
Zero-click

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
Storing Passwords in a Recoverable Format vulnerability in ABB Zenon 8.20 allows an attacker who successfully exploit the vulnerability may add more network clients that may monitor various activities of the Zenon.

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 confidence

ABB Zenon 8.20 stores user passwords in a recoverable (reversible) encryption format rather than using proper cryptographic hashing. This allows an attacker with database or file system access to recover plaintext passwords. The CVSS 6.1 score reflects low complexity and network adjacency requirements, with high confidentiality impact since exposed passwords can be reused for further compromise.

MitigationMigrate password storage to proper salted hashing (e.g., bcrypt, Argon2, scrypt) and implement least-privilege access controls to prevent unauthorized addition of network monitoring clients.

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
ZenonApplication
Affected:<= 8.20

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify ABB Zenon installation and version
    Check the installed Zenon version through the Windows Add/Remove Programs list, or look for Zenon installation directories (typically under C:\Program Files\COPA-DATA\ or C:\Program Files\ABB\) and locate version information in About or readme files
    Affected if Version is 8.20 or lower (any version up to and including 8.20)
  2. Locate Zenon user credential storage
    Identify database files (SQLite, SQL Compact, or other DB files) or configuration XML/ini files in the Zenon installation directory or program data folders that store user account information
    Affected if User credential storage files exist in the Zenon directory structure or associated databases
  3. Examine password storage format
    Open or query the user database/credential file and inspect the password field values. Determine whether passwords appear as: (a) plaintext, (b) encrypted (reversible algorithm), or (c) hashed (one-way function)
    Affected if Passwords are stored in an encrypted reversible format rather than using one-way cryptographic hash functions
  4. Check file system and database access controls
    Review file system permissions on Zenon configuration and database directories. Determine whether unauthorized users or processes can read these sensitive credential files
    Affected if World-readable permissions or weak ACLs exist on credential storage files, allowing database or file system access to low-privilege users

You are affected if ABB Zenon version 8.20 or lower is installed and user passwords are stored in a reversible encryption format (not one-way hashed) in accessible database or configuration files.

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.

From vendor data
Upgrade available Upgrade to a release after 8.20
Interim mitigation

Migrate password storage to proper salted hashing (e.g., bcrypt, Argon2, scrypt) and implement least-privilege access controls to prevent unauthorized addition of network monitoring clients.

Fix this in Zenon Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-34837 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