Symphony \+ HistorianApplication · Abb

CVE-2020-24673

CRITICAL · 9.8 CVSS v3.1 Published 2020-12-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
In S+ Operations and S+ Historian, a successful SQL injection exploit can read sensitive data from the database, modify database data (Insert/Update/Delete), execute administration operations on the database (such as shutdown the DBMS), recover the content of a given file present on the DBMS file system and in some cases issue commands to the operating system. This can lead to a loss of confidentiality and data integrity or even affect the product behavior and its availability.

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 confidence

SQL injection vulnerability in S+ Operations and S+ Historian allows attackers to read/modify/delete database contents, execute database administration operations, recover files from the DBMS filesystem, and in some cases execute OS-level commands. The critical severity (9.8) stems from the combination of network-exploitable attack vector and complete confidentiality/integrity impact.

MitigationImplement parameterized queries or prepared statements to remediate the SQL injection. Until patch is applied, restrict network access to these systems and apply least-principle database user permissions to limit exploitation impact.

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
Symphony \+ HistorianApplication
Affected:= 3.0= 3.1
Symphony \+ OperationsApplication
Affected:= 1.1= 2.0= 2.1= 3.0= 3.1= 3.2= 3.3

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if ABB S+ Historian or S+ Operations is installed
    Check system inventory, installed software list, or application directory for ABB Symphony+ components. Look for directories or services named 'S+ Historian' or 'S+ Operations' on the system.
    Affected if Either product is present on the system
  2. Determine installed version of ABB S+ Historian
    Check the application's about dialog, version information in the installation directory, or product documentation. Compare the version number against 3.0 and 3.1.
    Affected if Version is 3.0 or 3.1
  3. Determine installed version of ABB S+ Operations
    Check the application's about dialog, version information in the installation directory, or product documentation. Compare the version number against 1.1, 2.0, 2.1, 3.0, 3.1, 3.2, and 3.3.
    Affected if Version is 1.1, 2.0, 2.1, 3.0, 3.1, 3.2, or 3.3
  4. Verify if web interface or API is accessible
    Check network configuration to determine if the application's web interface or API endpoints are exposed to network access. Review firewall rules and service bindings.
    Affected if The application interface is network-accessible from untrusted locations

The environment is affected if ABB S+ Historian (versions 3.0-3.1) or S+ Operations (versions 1.1-3.3) is installed and the application interface is network-accessible, allowing attackers to inject malicious SQL queries through exposed input fields.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement parameterized queries or prepared statements to remediate the SQL injection. Until patch is applied, restrict network access to these systems and apply least-principle database user permissions to limit exploitation impact.

Fix this in Symphony \+ Historian Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-24673 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-24673 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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