800xa Information ManagerApplication · Abb

CVE-2020-8477

HIGH · 8.8 CVSS v3.1 Published 2020-04-22
Fix available
A fix is available. Upgrade to after 6.0.3.2 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
The installations for ABB System 800xA Information Manager versions 5.1, 6.0 to 6.0.3.2 and 6.1 wrongly contain an auxiliary component. An attacker is able to use this for an XSS-like attack to an authenticated local user, which might lead to execution of arbitrary code.

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

ABB System 800xA Information Manager versions 5.1, 6.0-6.0.3.2, and 6.1 contain an auxiliary component that introduces a vulnerability allowing XSS-like attacks against authenticated local users, potentially enabling arbitrary code execution.

MitigationIdentify and remove the auxiliary component from affected installations, or contact ABB for a patched version and guidance on secure configuration.

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
800xa Information ManagerApplication
Affected:>= 6.0.0, <= 6.0.3.2= 5.1= 6.1

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 installed ABB 800xA Information Manager version
    Check the product version through the Windows Add/Remove Programs list, or locate the version information in the installation directory's README or version file, or query the application's About dialog if accessible.
    Affected if The installed version is 5.1, any version from 6.0.0 through 6.0.3.2, or exactly version 6.1.
  2. Locate the auxiliary component directory
    Browse the ABB 800xA Information Manager installation folder (typically under C:\Program Files\ABB\ or C:\Program Files (x86)\ABB\) and locate subfolders or modules labeled as 'auxiliary', 'add-on', 'plugin', or similar. Check both the main application directory and any child directories named for optional components.
    Affected if The auxiliary component directory or module exists within the ABB installation folder.
  3. Verify the auxiliary component is present and enabled
    Inspect the auxiliary component's configuration files (look for .config, .xml, or .ini files in the component's directory) to confirm the component is installed. Check whether the component is referenced in any main application configuration files or manifests.
    Affected if The auxiliary component files are present and registered within the ABB Information Manager configuration.
  4. Check if the web interface or service is accessible
    Determine whether the ABB Information Manager web server or associated service is running and accessible. Check Windows Services for ABB-related services, or attempt to access the web interface on typical ports if exposed.
    Affected if The ABB Information Manager service or web interface is running and accepts authenticated user connections.

You are affected if your installed ABB 800xA Information Manager version falls within 5.1, 6.0-6.0.3.2, or 6.1, AND the vulnerable auxiliary component is present and enabled in your environment.

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
Upgrade available Upgrade to a release after 6.0.3.2
Interim mitigation

Identify and remove the auxiliary component from affected installations, or contact ABB for a patched version and guidance on secure configuration.

Fix this in 800xa Information Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,150
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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