CyberSecBulletin
CVE-2024-48847NVD status: Analyzed

ASPECT-Enterprise: Use of a Broken or Risky Cryptographic Algorithm

Published Updated By the CyberSecBulletin desk

CVE-2024-48847 is a critical-severity use of a broken or risky cryptographic algorithm vulnerability in ASPECT-Enterprise from ABB, with a CVSS 3.1 base score of 9.1 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected ASPECT-Enterprise versions: 3.08.01 and earlier. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.26% chance of exploitation within 30 days, which is low compared with other CVEs.

Patch this week

Critical severity: a successful attack would have severe impact.

What to do

  1. Update Aspect-ent-2 Firmware to 3.08.03 or a later version.
  2. Update Aspect-ent-256 Firmware to 3.08.03 or a later version.
  3. Update Aspect-ent-96 Firmware to 3.08.03 or a later version.
  4. Read the advisory on search.abb.com for workarounds and exact fixed builds.
  5. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
ABBASPECT-Enterprise3.08.01 and earlierNot stated
ABBNEXUS Series3.08.01 and earlierNot stated
ABBMATRIX Series3.08.01 and earlierNot stated
ABBAspect-ent-2 Firmwarebefore 3.08.033.08.03
ABBAspect-ent-256 Firmwarebefore 3.08.033.08.03
ABBAspect-ent-96 Firmwarebefore 3.08.033.08.03
ABBNexus-2128 Firmwarebefore 3.08.033.08.03
ABBNexus-2128-a Firmwarebefore 3.08.033.08.03
ABBNexus-2128-f Firmwarebefore 3.08.033.08.03
ABBNexus-2128-g Firmwarebefore 3.08.033.08.03
ABBNexus-264 Firmwarebefore 3.08.033.08.03
ABBNexus-264-a Firmwarebefore 3.08.033.08.03
ABBNexus-264-g Firmwarebefore 3.08.033.08.03
ABBNexus-3-2128 Firmwarebefore 3.08.033.08.03
ABBAspect-ent-12 Firmware3.08.01 and earlierNot stated
ABBNexus-264-f Firmwarebefore 3.08.033.08.03
ABBNexus-3-264 Firmware3.08.01 and earlierNot stated
ABBMatrix-11 Firmware3.08.01 and earlierNot stated
ABBMatrix-216 Firmware3.08.01 and earlierNot stated
ABBMatrix-232 Firmware3.08.01 and earlierNot stated
ABBMatrix-264 Firmware3.08.01 and earlierNot stated
ABBMatrix-296 Firmware3.08.01 and earlierNot stated

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
NoneAvailability is not affected.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 4.08.8HighCNA (ch.abb.com)
CVSS 3.18.2HighCNA (ch.abb.com)
CVSS 3.19.1CriticalNVD

Official description

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

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Use of a Broken or Risky Cryptographic Algorithm

The product uses a broken or risky cryptographic algorithm or protocol.

How developers prevent this class of flaw

  • Ensure that the design allows one cryptographic algorithm to be replaced with another in the next generation or version. Where possible, use wrappers to make the interfaces uniform. This will make it easier to upgrade to stronger algorithms. With hardware, design the product at the Intellectual Property (IP) level so that one cryptographic algorithm can be replaced with another in the next generation of the hardware product.
  • Carefully manage and protect cryptographic keys (see CWE-320). If the keys can be guessed or stolen, then the strength of the cryptography itself is irrelevant.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Industry-standard implementations will save development time and may be more likely to avoid errors that can occur during implementation of cryptographic algorithms. Consider the ESAPI Encryption feature.

More Use of a Broken or Risky Cryptographic Algorithm vulnerabilities (CWE-327)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in ASPECT-Enterprise

All ASPECT-Enterprise vulnerabilities

Recent Use of a Broken or Risky Cryptographic Algorithm vulnerabilities

Spotted an error? Tell us.