dbcve.org
Aspect Ent 2 FirmwareOperating system · Abb

CVE-2023-0635

CRITICAL · 9.8 CVSS v3.1 Published 2023-06-05
Fix available
A fix is available. Upgrade to 3.07.01 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
Improper Privilege Management vulnerability in ABB Ltd. ASPECT®-Enterprise on ASPECT®-Enterprise, Linux (2CQG103201S3021, 2CQG103202S3021, 2CQG103203S3021, 2CQG103204S3021 modules), ABB Ltd. NEXUS Series on NEXUS Series, Linux (2CQG100102R2021, 2CQG100104R2021, 2CQG100105R2021, 2CQG100106R2021, 2CQG100110R2021, 2CQG100112R2021, 2CQG100103R2021, 2CQG100107R2021, 2CQG100108R2021, 2CQG100109R2021, 2CQG100111R2021, 2CQG100113R2021 modules), ABB Ltd. MATRIX Series on MATRIX Series, Linux (2CQG100102R1021, 2CQG100103R1021, 2CQG100104R1021, 2CQG100105R1021, 2CQG100106R1021 modules) allows Privilege Escalation.This issue affects ASPECT®-Enterprise: from 3.0;0 before 3.07.01; NEXUS Series: from 3.0;0 before 3.07.01; MATRIX Series: from 3.0;0 before 3.07.01.

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

Improper privilege management in ABB ASPECT-Enterprise, NEXUS Series, and MATRIX Series industrial control software allows authenticated attackers to escalate privileges to administrative levels. This vulnerability affects versions 3.0 through 3.07.00 across all three product lines, enabling potential full system compromise.

MitigationUpgrade to version 3.07.01 or later to remediate this privilege escalation vulnerability. For production environments, develop a change management plan and test the upgrade in a staging environment before 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
Aspect Ent 2 FirmwareOperating system
Affected:>= 3.0.0, < 3.07.01
Aspect Ent 12 FirmwareOperating system
Affected:>= 3.0.0, < 3.07.01
Aspect Ent 256 FirmwareOperating system
Affected:>= 3.0.0, < 3.07.01
Aspect Ent 96 FirmwareOperating system
Affected:>= 3.0.0, < 3.07.01
Nexus 2128 FirmwareOperating system
Affected:>= 3.0.0, < 3.07.01
Nexus 2128 A FirmwareOperating system
Affected:>= 3.0.0, < 3.07.01
Nexus 2128 G FirmwareOperating system
Affected:>= 3.0.0, < 3.07.01
Nexus 2128 F FirmwareOperating system
Affected:>= 3.0.0, < 3.07.01

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 the ABB product model
    Locate the system documentation, HMI interface, or check the device label to determine if the product is one of: ASPECT-Enterprise (models 2, 12, 96, 256), NEXUS Series (2128, 2128 A, 2128 G, 2128 F), or MATRIX Series
    Affected if The device is any of these ABB product lines
  2. Retrieve the installed firmware version
    Access the device admin panel, system information screen, or use the device's web interface to view the firmware version. The exact method varies by product but is typically found under Settings, System Info, or About sections
    Affected if Unable to determine the version (unverified product status)
  3. Compare version against affected range
    Check if the installed version is >= 3.0.0 and < 3.07.01. Versions 3.0.0 through 3.07.00 are all affected
    Affected if The installed version falls within >= 3.0.0 and < 3.07.01

A user is affected if they are running ABB ASPECT-Enterprise, NEXUS Series, or MATRIX Series firmware versions 3.0.0 through 3.07.00 (versions below 3.07.01).

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 3.07.01 or later
Fixed in 3.07.01
Interim mitigation

Upgrade to version 3.07.01 or later to remediate this privilege escalation vulnerability. For production environments, develop a change management plan and test the upgrade in a staging environment before deployment.

Recommended fix High confidence

Firmware version 3.07.01 or later for Aspect Enterprise, Nexus Series, and MATRIX Series

  1. 1. Identify the specific ABB device model (Aspect Enterprise or Nexus Series) and current firmware version using the device interface or administrative console.
  2. 2. Navigate to the ABB software download portal at search.abb.com or contact ABB Technical Support to obtain firmware version 3.07.01 or later.
  3. 3. Review ABB's official firmware upgrade documentation for your specific device model before proceeding.
  4. 4. Create a full backup of the current device configuration according to ABB's backup procedures.
  5. 5. Ensure the upgrade process has a stable power supply and network connection to prevent interruption.
  6. 6. Upload and apply firmware version 3.07.01 or later using the device's firmware update functionality.
  7. 7. After the firmware upgrade completes, verify the new firmware version is correctly installed.
  8. 8. Restore the device configuration from the backup taken in step 4.
Caveat Review ABB release notes for version 3.07.01 to check for any configuration or behavioral changes that may affect your deployment

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

Fix this in Aspect Ent 2 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing24.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,520
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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