CVERadar
CRITICAL · CVSS 4.0 9.4Exploit-DBEPSS 17.16% (p97)Threat level 59

CVE-2024-6209: CVE-2024-6209: Unauthorized file access in WEB Server in ABB ASPECT - Enterprise v3.08.01; NEXUS Series …

abb · aspect-ent-12 firmware · NVD published 2024-07-05 · posted 2025-04-02 · last modified 2026-06-17

What it is

Unauthorized file access in WEB Server in ABB ASPECT - Enterprise v3.08.01; NEXUS Series v3.08.01 ; MATRIX Series v3.08.01 allows Attacker to access files unauthorized

WeaknessCWE-552
CVSS vectorCVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:Y/R:I/V:C/RE:H/U:Red (source: [email protected])
ATT&CK tacticsn/a

Exploitation evidence

First exploit evidence seen: 2025-04-02 (earliest date across the sources below).

Exploited in the wild

No source on this site lists in-the-wild exploitation yet (CISA KEV, VulnCheck KEV).

Public exploit code

Exploit-DB

  • EDB-52108: ABB Cylon Aspect 3.08.01 - Arbitrary File Delete (2025-04-02)

Sources: Exploit-DB (OffSec).

No ATT&CK techniques could be mapped or inferred for this CVE yet.

How to fix it

Fixed versions

  • abb aspect-ent-12 firmware: versions up to and including 3.08.01 are affected; check the vendor advisory for the fixed release.
  • abb aspect-ent-2 firmware: versions up to and including 3.08.01 are affected; check the vendor advisory for the fixed release.
  • abb aspect-ent-256 firmware: versions up to and including 3.08.01 are affected; check the vendor advisory for the fixed release.
  • abb aspect-ent-96 firmware: versions up to and including 3.08.01 are affected; check the vendor advisory for the fixed release.
  • abb nexus-2128 firmware: versions up to and including 3.08.01 are affected; check the vendor advisory for the fixed release.
  • abb nexus-2128-a firmware: versions up to and including 3.08.01 are affected; check the vendor advisory for the fixed release.
  • abb nexus-2128-f firmware: versions up to and including 3.08.01 are affected; check the vendor advisory for the fixed release.
  • abb nexus-2128-g firmware: versions up to and including 3.08.01 are affected; check the vendor advisory for the fixed release.
  • abb nexus-264 firmware: versions up to and including 3.08.01 are affected; check the vendor advisory for the fixed release.
  • abb nexus-264-a firmware: versions up to and including 3.08.01 are affected; check the vendor advisory for the fixed release.
  • abb nexus-264-f firmware: versions up to and including 3.08.01 are affected; check the vendor advisory for the fixed release.
  • abb nexus-264-g firmware: versions up to and including 3.08.01 are affected; check the vendor advisory for the fixed release.
  • abb nexus-3-2128 firmware: versions up to and including 3.08.01 are affected; check the vendor advisory for the fixed release.
  • abb nexus-3-264 firmware: versions up to and including 3.08.01 are affected; check the vendor advisory for the fixed release.
  • abb matrix-11 firmware: versions up to and including 3.08.01 are affected; check the vendor advisory for the fixed release.
  • abb matrix-216 firmware: versions up to and including 3.08.01 are affected; check the vendor advisory for the fixed release.
  • abb matrix-232 firmware: versions up to and including 3.08.01 are affected; check the vendor advisory for the fixed release.
  • abb matrix-264 firmware: versions up to and including 3.08.01 are affected; check the vendor advisory for the fixed release.
  • abb matrix-296 firmware: versions up to and including 3.08.01 are affected; check the vendor advisory for the fixed release.

Derived from the NVD CPE configuration (versionEndExcluding / versionEndIncluding). Always confirm with the vendor advisory.

Vendor advisories and patches

Detection Generic guidance

    Response checklist Generic guidance

    1. Inventory: find every instance of the affected product and version (include internet-facing and forgotten ones).
    2. Patch or mitigate per the vendor advisory; if you cannot patch, remove internet exposure or apply the vendor workaround.
    3. Assume compromise if the system was exposed before patching: hunt for the indicators in the advisory and review logs back to the disclosure date.
    4. Rotate credentials and secrets stored on or used by the affected system if compromise cannot be ruled out.

    Sources