CVE-2020-24675
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 S+ Operations and S+ History, it is possible that an unauthenticated user could inject values to the Operations History server (or standalone S+ History server) and ultimately write values to the controlled process.
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 confidenceThis is an unauthenticated injection vulnerability in Siemens S+ Operations and S+ History (ICS/OT systems). An attacker can send specially crafted values to the Operations History server that get written to the controlled industrial process, effectively allowing manipulation of process values without any authentication. The critical CVSS score reflects the network-exploitable, no-authentication-required nature with direct process manipulation capability.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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+ productsReview system inventory or installed software list for ABB Symphony+ Operations or ABB Symphony+ Historian componentsAffected if Either product is present on the system
-
Determine product version numbersLocate the version information for the installed ABB Symphony+ Operations or Historian component (typically found in the product About section, installation directory, or system services)Affected if 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
-
Verify History server network exposureCheck network configuration to determine if the Operations History server component is accessible from the network (review firewall rules, exposed ports, and network interfaces bound to the History service)Affected if The History server component listens on a network-accessible interface without authentication restrictions
-
Review process value change logsExamine the operations and history logs for unauthorized or unexpected process value modifications that occur without corresponding authenticated user actionsAffected if Process values were modified without legitimate authenticated user activity
-
Check for unauthorized historical recordsQuery the Historian database or logs for timestamps and sources of process data changes that do not match expected operational patternsAffected if Historical records show process modifications originating from unauthenticated or unexpected sources
A defender is affected if they have ABB Symphony+ Operations version 1.1 through 3.3 or Historian version 3.0 or 3.1 running with the History server component exposed to the network.
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 dataIsolate the S+ History servers behind a DMZ with strict network segmentation, apply vendor patches when available, and implement monitoring for unauthorized process value changes. If patching is not immediately feasible, disable unauthenticated network access to the History server components.
- Consultation12.0 h
- Implementation20.0 h
- Testing16.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-24675 — 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-24675 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