CVE-2020-6968
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 · uneditedHoneywell INNCOM INNControl 3 allows workstation users to escalate application user privileges through the modification of local configuration files.
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 Honeywell INNCOM INNControl 3 building automation system contains a local privilege escalation vulnerability where workstation users with standard application privileges can modify local configuration files to gain elevated user privileges within the application. The attack vector is local (AV:L), requires low privileges (PR:L), and achieves high confidentiality, integrity, and availability impact (C:H/I:H/A:H).
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, <= 3.21CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
-
Determine the installed firmware versionAccess the system administration interface or use the device's built-in version check command (such as 'show version' or through the web management console) to retrieve the current firmware version. Compare this against the affected range: versions 3.0 through 3.21.Affected if The firmware version falls within 3.0 to 3.21 inclusive.
-
Identify user account types in the applicationReview the INNControl 3 user management section to list all defined user accounts and their assigned privilege levels. Look for accounts assigned standard or limited application privileges versus administrative roles.Affected if Standard (non-administrative) user accounts exist in the system.
-
Verify file system permissions on configuration filesExamine the file system permissions on the local configuration directories and files used by the INNControl 3 application. Use operating system commands (such as 'ls -l' or icacls on Windows) to list access control entries.Affected if Standard user accounts have write permissions to configuration files that should be restricted to administrators.
-
Confirm if standard users can modify application configurationAttempt to access the configuration modification interface using a standard (non-privileged) user account, or review the application's role-based access control settings to determine which privilege levels can alter configuration files.Affected if Standard users are permitted to save or modify configuration files through the application interface.
A user is affected if they are running firmware version 3.0 through 3.21 AND the system allows standard application users to write to configuration files that should be restricted to administrators.
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 dataRestrict write access to configuration files to privileged administrators only, implement file integrity monitoring, and apply principle of least privilege to the application's user role permissions.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-6968 — 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-2020-6968 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