dbcve.org
Aspect Ent 2 FirmwareOperating system · Abb

CVE-2024-48847

CRITICAL · 9.1 CVSS v3.1 Published 2024-12-05
Fix available
A fix is available. Upgrade to 3.08.03 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
MD5 Checksum Bypass vulnerabilities where found exploiting a weakness in the way an application dependency calculates or validates MD5 checksum hashes.  Affected products: ABB ASPECT - Enterprise v3.08.01; NEXUS Series v3.08.01; MATRIX Series v3.08.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 · moderate confidence

MD5 checksum bypass vulnerability in ABB ASPECT Enterprise, NEXUS Series, and MATRIX Series v3.08.01 allows attackers to exploit weak validation logic in an application dependency to bypass integrity checks, potentially enabling tampered code or data to be accepted as legitimate.

MitigationUpdate to vendor-patched version if available; otherwise implement additional integrity verification using stronger hash algorithms (SHA-256 or above) and apply network segmentation to reduce attack surface.

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.08.03
Aspect Ent 256 FirmwareOperating system
Affected:< 3.08.03
Aspect Ent 96 FirmwareOperating system
Affected:< 3.08.03
Nexus 2128 FirmwareOperating system
Affected:< 3.08.03
Nexus 2128 A FirmwareOperating system
Affected:< 3.08.03
Nexus 2128 F FirmwareOperating system
Affected:< 3.08.03
Nexus 2128 G FirmwareOperating system
Affected:< 3.08.03
Nexus 264 FirmwareOperating system
Affected:< 3.08.03

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
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

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 device model
    Access the ABB device console or management interface and retrieve the model identifier (Aspect Enterprise 2/96/256 or Nexus 2128/2128 A/2128 F/2128 G/264)
    Affected if The device is not one of the listed ABB ASPECT Enterprise or NEXUS Series models
  2. Check the installed firmware version
    Execute the appropriate command to display firmware version (e.g., 'show version', 'system info', or via the device web interface under firmware or system status)
    Affected if The firmware version cannot be determined or is not visible
  3. Compare firmware version to affected range
    Review the firmware version number and confirm it is < 3.08.03 for the specific model identified in step 1
    Affected if The firmware version is 3.08.01 or any version below 3.08.03 on an affected model
  4. Identify MD5 checksum usage in the application
    Inspect application logs, configuration files, or firmware update manifests for references to MD5 hash validation (search for 'MD5' in configuration files or update packages)
    Affected if MD5 checksums are actively used for validating firmware, configuration, or data files

A defender is affected if their ABB ASPECT Enterprise or NEXUS Series device runs firmware version 3.08.01 or below AND uses MD5 for checksum validation.

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.08.03 or later
Fixed in 3.08.03
Interim mitigation

Update to vendor-patched version if available; otherwise implement additional integrity verification using stronger hash algorithms (SHA-256 or above) and apply network segmentation to reduce attack surface.

Recommended fix High confidence

Firmware version 3.08.03 or later for Aspect Ent 2/256/96 and Nexus 2128/2128A/2128F/2128G/264 series

  1. 1. Identify the exact ABB product model (Aspect Ent 2/256/96 or Nexus 2128/2128A/2128F/2128G/264) from the affected list
  2. 2. Obtain the firmware version 3.08.03 or later from ABB's official firmware distribution channel (search.abb.com or ABB support)
  3. 3. Review ABB product documentation for firmware upgrade procedures specific to your device model
  4. 4. Create a backup of the current device configuration if supported
  5. 5. Follow ABB's documented firmware update procedure for the specific device, typically involving uploading the firmware file through the device's management interface
  6. 6. After upgrade, verify the firmware version has been updated to 3.08.03 or later
  7. 7. Verify that all MD5 checksum validations are functioning correctly post-upgrade
Caveat Industrial control设备固件升级可能影响实时操作，建议在维护窗口期进行，并预先测试兼容性

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

Fix this in Aspect Ent 2 Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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