CVE-2020-24676
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 · uneditedIn Symphony Plus Operations and Symphony Plus Historian, some services can be vulnerable to privilege escalation attacks. An unprivileged (but authenticated) user could execute arbitrary code and result in privilege escalation, depending on the user that the service runs as.
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 confidenceIn Symphony Plus Operations and Symphony Plus Historian, certain services contain flaws that allow an authenticated but unprivileged user to execute arbitrary code. This code runs with the privileges of the service account, enabling privilege escalation to potentially SYSTEM or other high-privilege users.
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
- 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.
-
Identify installed Symphony Plus productsCheck the system for installed ABB Symphony Plus applications. Look for 'Symphony Plus Historian' or 'Symphony Plus Operations' in Program Files, Program Files (x86), or the Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\UninstallAffected if Either Symphony Plus Historian or Symphony Plus Operations is installed and the version matches 3.0 or 3.1 for Historian, or 1.1, 2.0, 2.1, 3.0, 3.1, 3.2, or 3.3 for Operations
-
Determine the exact installed versionOpen Windows Control Panel > Programs and Features, or run 'Get-WmiObject Win32_Product' (PowerShell) to list installed software and their version numbers. Look for the Version column entry matching the affected productsAffected if The installed version number exactly matches 3.0 or 3.1 for Historian, or 1.1, 2.0, 2.1, 3.0, 3.1, 3.2, or 3.3 for Operations
-
Check service account privilegesOpen Services console (services.msc), locate the Symphony Plus Historian or Operations service, right-click and select Properties, then check the 'Log On' tab. Note the account under which the service runsAffected if The service runs under a high-privilege account such as LocalSystem, a domain administrator account, or any account with elevated permissions beyond what the authenticated user role requires
-
Verify accessible service endpointsCheck if the Symphony Plus service ports or endpoints are accessible to authenticated but non-administrative users on the network. Use netstat -an | findstr 'LISTENING' to identify listening ports associated with the product, then confirm which user groups can reach those endpointsAffected if Service endpoints are accessible to authenticated users who do not have administrative or elevated privileges on the system
A defender is affected if Symphony Plus Historian version 3.0 or 3.1, or Symphony Plus Operations version 1.1 through 3.3, is installed and the service runs with elevated privileges accessible to low-privilege authenticated users.
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 service permissions to minimum necessary, review and harden service configurations, implement least-privilege service accounts, and apply vendor patches when available.
- Consultation8.0 h
- Implementation16.0 h
- Testing8.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 $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-24676 — 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-24676 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