CVE-2024-6298: CVE-2024-6298: 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 execute arbitrary code remotely
| Weakness | CWE-1287 |
|---|---|
| CVSS vector | CVSS: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 tactics | Initial Access → Execution |
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-52107: ABB Cylon Aspect 3.08.01 - Remote Code Execution (RCE) (2025-04-02)
Sources: Exploit-DB (OffSec).
Defend the Chain
The attack chain for CVE-2024-6298 laid across the MITRE ATT&CK Enterprise tactics. Solid cards come from the MITRE CTID KEV mappings; dashed cards are inferred by CVERadar from the CWE or description. Correct defences are real ATT&CK mitigations for that technique.
Pick a red technique card on the board, then choose the defence that stops it.
Defend against T1190 Exploit Public-Facing Application Inferred
Inferred from description keywords
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
MITRE ATT&CK mitigations for this chain
- M1048 Application Isolation and Sandboxing (for T1190, T1203) : Application isolation will limit what other processes and system features the exploited target can access.
- M1037 Filter Network Traffic (for T1190) : Restrict outbound network traffic from public-facing servers to prevent unauthorized connections from initiating communications with attacker-controlled infrastructure. While this may not prevent the initial exploitation, it limits the attacker's ability to verify and control the compromised server post-exploit, reduci
- M1030 Network Segmentation (for T1190) : Segment externally facing servers and services from the rest of the network with a DMZ or on separate hosting infrastructure.
- M1016 Vulnerability Scanning (for T1190) : Regularly scan externally facing systems for vulnerabilities and establish procedures to rapidly patch systems when critical vulnerabilities are discovered through scanning and through public disclosure.
- M1026 Privileged Account Management (for T1190) : Use least privilege for service accounts will limit what permissions the exploited process gets on the rest of the system.
- M1050 Exploit Protection (for T1190, T1203) : Web Application Firewalls may be used to limit exposure of applications to prevent exploit traffic from reaching the application.
- M1035 Limit Access to Resource Over Network (for T1190) : Ensure that all publicly exposed services are actually intended to be so, and restrict access to any that should only be available internally.
- M1051 Update Software (for T1190, T1203) : Update software regularly by employing patch management for externally exposed applications.
Detection Generic guidance
- Initial Access: Alert on unusual requests to the affected service (odd paths, oversized payloads, exploit strings) in WAF, reverse-proxy and application logs.
- Execution: Watch for the service process spawning shells or script interpreters (cmd.exe, powershell, sh, bash, python) via EDR process-tree rules.
Response checklist Generic guidance
- Inventory: find every instance of the affected product and version (include internet-facing and forgotten ones).
- Patch or mitigate per the vendor advisory; if you cannot patch, remove internet exposure or apply the vendor workaround.
- Assume compromise if the system was exposed before patching: hunt for the indicators in the advisory and review logs back to the disclosure date.
- Rotate credentials and secrets stored on or used by the affected system if compromise cannot be ruled out.