dbcve.org
Aspect Ent 12 FirmwareOperating system · Abb

CVE-2024-51549

CRITICAL · 9.4 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
Absolute File Traversal vulnerabilities allows access and modification of un-intended resources.  Affected products: ABB ASPECT - Enterprise v3.08.02; NEXUS Series v3.08.02; MATRIX Series v3.08.02

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

Absolute file traversal vulnerability in ABB ASPECT Enterprise, NEXUS Series, and MATRIX Series v3.08.02 allows attackers to escape intended directory constraints and access/modify system files beyond the application's root, likely via unsanitized path inputs in HTTP requests.

MitigationRestrict network exposure of affected systems, implement strict input validation enforcing allowed paths, and monitor for unauthorized file access patterns; consult ABB for available patches.

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 12 FirmwareOperating system
Affected:< 3.08.03
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

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
Low

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

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. Check firmware version
    Access the device web interface or use SNMP/sysinfo commands to retrieve the current firmware version. Look for version information in the system status or about page.
    Affected if Firmware version is less than 3.08.03 (e.g., 3.08.02, 3.08.01, etc.)
  2. Identify file handling functionality
    Locate any file upload, file download, file viewing, or file export features in the web interface. Check for endpoints that accept file path parameters.
    Affected if File handling features that accept path parameters are accessible and enabled on the device
  3. Verify web service is running
    Confirm the embedded web server (HTTP/HTTPS service) is active and accessible on the device.
    Affected if The web interface is exposed and operational, providing access to the vulnerable file handling code
  4. Check for absolute path input acceptance
    Test or inspect file-related web endpoints to determine if they accept absolute file paths without strict validation. Review any available configuration or logs for path input handling.
    Affected if The system accepts absolute path inputs in file operations without proper path validation or canonicalization

The device is affected if it runs firmware version prior to 3.08.03 AND exposes file handling functionality through its web interface that accepts file path inputs.

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

Restrict network exposure of affected systems, implement strict input validation enforcing allowed paths, and monitor for unauthorized file access patterns; consult ABB for available patches.

Recommended fix High confidence

Firmware version 3.08.03 for all affected Aspect Enterprise and Nexus series devices

  1. Identify the specific affected device model (Aspect Enterprise 12, 2, 96, 256, or Nexus 2128/2128A/2128F/2128G) from the product lineup
  2. Access the device administrative interface or firmware management system
  3. Locate the firmware update section within the device management interface
  4. Download firmware version 3.08.03 from the official ABB support portal at search.abb.com
  5. Verify the firmware integrity using any provided checksums
  6. Initiate the firmware upgrade process, ensuring stable power supply throughout
  7. Allow the device to fully complete the boot cycle after upgrade
  8. Verify the firmware version has been updated to 3.08.03
Caveat Review ABB release notes for any configuration or behavioral changes between 3.08.02 and 3.08.03

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

Fix this in Aspect Ent 12 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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