dbcve.org
Tristation 1131Application · Schneider Electric

CVE-2020-7485

CRITICAL · 9.8 CVSS v3.1 Published 2020-04-16
Fix available
A fix is available. Upgrade to after 4.9.0 or later.
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
**VERSION NOT SUPPORTED WHEN ASSIGNED** A legacy support account in the TriStation software version v4.9.0 and earlier could cause improper access to the TriStation host machine. This was addressed in TriStation version v4.9.1 and v4.10.1 released on May 30, 2013.1

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 confidence

A legacy support account in TriStation software v4.9.0 and earlier allows improper/unauthorized access to the host machine due to improper access controls. This is a critical authentication bypass/privilege escalation vulnerability affecting an industrial control system programming tool.

MitigationUpgrade TriStation software to version v4.9.1 or v4.10.1 or later to remove the vulnerable legacy support account. In ICS environments, validate the upgrade in a test environment before production deployment.

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
Tristation 1131Application
Affected:>= 1.0.0, <= 4.9.0= 4.10.0= 4.12.0

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 TriStation 1131 is installed
    Check for TriStation installation directory (commonly C:\Program Files\Schneider Electric\TriStation or C:\TriStation) and look for ts1131.exe or related executables
    Affected if TriStation software is found on the system
  2. Determine installed TriStation version
    Right-click the TriStation executable, select Properties, then Details tab to view File Version; or open TriStation and check Help > About TriStation 1131
    Affected if Version is >= 1.0.0 and <= 4.9.0, or equals 4.10.0, or equals 4.12.0
  3. Check for legacy support account
    Examine Windows local user accounts on the machine where TriStation is installed; look for accounts with names like 'support', 'service', 'admin', 'tristation', or other undocumented service accounts
    Affected if A legacy support or service account exists that was not created by your organization or documented in your system documentation
  4. Verify account access permissions
    Use Computer Management > Local Users and Groups to check if the legacy account has administrative privileges or remote desktop access that should not be present
    Affected if The legacy support account has elevated privileges or unauthorized access rights

If TriStation 1131 version 4.9.0 or earlier, 4.10.0, or 4.12.0 is installed with an undocumented legacy support account present, the environment is affected by this vulnerability.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 4.9.0
Interim mitigation

Upgrade TriStation software to version v4.9.1 or v4.10.1 or later to remove the vulnerable legacy support account. In ICS environments, validate the upgrade in a test environment before production deployment.

Recommended fix Moderate confidence

Upgrade to TriStation v4.9.1 or v4.10.1

  1. Identify the current Tristation 1131 version in use
  2. Upgrade to TriStation version v4.9.1 or v4.10.1 (both contain the fix for the legacy support account vulnerability)
  3. After upgrade, verify the legacy support account has been removed or disabled
  4. Change credentials for all remaining accounts as a security best practice
  5. Confirm the upgrade was successful by checking the software version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Tristation 1131 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,780
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-7485 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-7485 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