CVE-2020-24678
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 · uneditedAn authenticated user might execute malicious code under the user context and take control of the system. S+ Operations or S+ Historian database is affected by multiple vulnerabilities such as the possibility to allow remote authenticated users to gain high privileges.
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 confidenceAuthenticated users can execute malicious code under their user context in S+ Operations or S+ Historian database software, potentially achieving system-level control through privilege escalation vulnerabilities that allow remote authenticated users to gain elevated privileges.
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.1= 1.1= 2.0= 2.1= 3.0= 3.1= 3.2= 3.3CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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.
-
Identify installed ABB Symphony+ productsCheck for ABB Symphony+ Historian or Operations software on the system by examining installed programs (Windows: Registry key HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall or Programs and Features; Linux: package manager listings or /opt directory for ABB software)Affected if Either Symphony+ Historian or Operations software is present on the system
-
Determine Symphony+ Historian versionLocate the Historian installation directory (commonly C:\Program Files\ABB\SymphonyPlus\Historian or /opt/abb/symphonyplus/historian) and check for a version file, or run the product's about/version information command if availableAffected if Version is 3.0 or 3.1
-
Determine Symphony+ Operations versionLocate the Operations installation directory (commonly C:\Program Files\ABB\SymphonyPlus\Operations or /opt/abb/symphonyplus/operations) and check for a version file, or run the product's about/version information command if availableAffected if Version is 1.1, 2.0, 2.1, 3.0, 3.1, 3.2, or 3.3
-
Verify authentication is enabledCheck if user authentication is configured for the Symphony+ web interface or client services. Review authentication settings in the product configuration files or management consoleAffected if User authentication is enabled and user accounts exist in the system (authenticated user access is required for exploitation)
You are affected if ABB Symphony+ Historian version 3.0 or 3.1, OR Symphony+ Operations versions 1.1 through 3.3 are installed AND user authentication is enabled, allowing authenticated users to potentially execute code and escalate privileges.
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 authentication access through least-privilege principles, implement network segmentation to limit exposure, apply vendor security updates when available, and monitor for anomalous authenticated session behavior indicating privilege abuse.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.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,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-24678 — 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-24678 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