CVE-2022-0835
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 · uneditedAVEVA System Platform 2020 stores sensitive information in cleartext, which may allow access to an attacker or a low-privileged user.
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 confidenceAVEVA System Platform 2020 contains a vulnerability where sensitive information is stored in cleartext, enabling attackers or low-privileged users to directly access confidential data without requiring decryption. This represents a data-at-rest confidentiality breach in an industrial control system platform.
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= 2020CVSS 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.
-
Verify AVEVA System Platform versionCheck the installed version of AVEVA System Platform in the system registry, installation directory, or via the Aveva Information dialog (typically found in Help > About). Compare the version to '2020'.Affected if The installed version is exactly 2020
-
Identify sensitive data storage locationsLocate configuration files, XML files, and database files used by AVEVA System Platform 2020. These typically include project configuration files, security settings, and user credential storage areas.Affected if Sensitive data storage locations exist and are accessible to the application
-
Inspect credential and configuration storageExamine the contents of configuration files and database files for stored credentials, passwords, keys, or other sensitive data. Look for plaintext strings that appear to be passwords, API keys, or confidential parameters.Affected if Credentials, passwords, or other sensitive data are found in cleartext (unencrypted) format within configuration files or databases
-
Verify encryption status of sensitive dataCheck if the identified sensitive data appears encrypted (encoded, hashed, or scrambled characters) or in plaintext readable format. Use a hex editor or text viewer to inspect raw file contents.Affected if Sensitive data is stored in readable plaintext rather than being encrypted or hashed
A user is affected if AVEVA System Platform 2020 is installed and sensitive data such as credentials or configuration secrets are stored in unencrypted cleartext format.
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.
From vendor dataImplement encryption for sensitive data storage locations within AVEVA System Platform 2020, ensure proper access controls are enforced, and consider upgrading to a patched version if available.
- Consultation6.0 h
- Implementation20.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-0835 — 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-0835 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