CVE-2022-0010
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 · uneditedInsertion of Sensitive Information into Log File vulnerability in ABB QCS 800xA, ABB QCS AC450, ABB Platform Engineering Tools. An attacker, who already has local access to the QCS nodes, could successfully obtain the password for a system user account. Using this information, the attacker could have the potential to exploit this vulnerability to gain control of system nodes. This issue affects QCS 800xA: from 1.0;0 through 6.1SP2; QCS AC450: from 1.0;0 through 5.1SP2; Platform Engineering Tools: from 1.0:0 through 2.3.0.
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 confidenceSensitive information (system user passwords) is being written to log files in ABB QCS 800xA, ABB QCS AC450, and Platform Engineering Tools. An attacker with local access to QCS nodes can read these log files to obtain credentials and potentially gain control of system nodes.
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>= 1.0.0, <= 2.3.0>= 1.0.0, <= 5.1.0= 5.1.0>= 1.0.0, <= 6.1.0= 6.1.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
- 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 installed ABB product and versionLocate the ABB software installation directory or check system inventory for Platform Engineering Tools, QCS 800xA, or QCS AC450. Obtain the exact version number from the product documentation, about dialog, or version file.Affected if The installed version falls within 1.0.0 to 2.3.0 for Platform Engineering Tools, 1.0.0 to 5.1.0 for QCS 800xA, or 1.0.0 to 6.1.0 for QCS AC450.
-
Locate QCS log directoriesSearch for log directories commonly used by ABB QCS products, such as C:\ProgramData\ABB\QCS\Logs, /var/log/abb/qcs/, or the logs folder within the QCS installation directory. Use file system search tools to find directories named 'logs' or 'log' within ABB installation paths.Affected if Log directories exist and contain log files from the affected product versions.
-
Search log files for password patternsUse grep, Select-String, or similar text search tools to scan log files for password strings. Look for patterns such as 'password', 'pwd', 'passwd', or base64-encoded strings that may represent credentials. Example command: grep -r -i 'password\|pwd\|passwd' /path/to/logs/*.logAffected if Log files contain plaintext or encoded password strings, system user credentials, or authentication tokens.
-
Verify file access controls on log directoriesCheck file permissions on identified log directories using icacls (Windows) or ls -la (Linux/Unix). Determine which user accounts have read access to these directories.Affected if Non-privileged or unauthorized local user accounts have read access to directories containing sensitive log files.
A system is affected if it runs any of the affected ABB product versions AND contains log files readable by unauthorized users that expose system passwords or credentials.
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 dataUpgrade to vendor-patched versions if available. Immediately change any passwords that may have been exposed in logs, restrict access to log file directories, and review log configurations to prevent credential leakage.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-0010 — 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-0010 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