CVE-2024-51548
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 · uneditedDangerous File Upload vulnerabilities allow upload of malicious scripts. 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 confidenceA dangerous file upload vulnerability in ABB ASPECT Enterprise, NEXUS Series, and MATRIX Series v3.08.02 allows attackers to upload malicious scripts to the affected systems. This could enable remote code execution or other attacks by leveraging the uploaded malicious files.
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< 3.08.03< 3.08.03< 3.08.03< 3.08.03< 3.08.03< 3.08.03< 3.08.03< 3.08.03CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify the ABB device modelLocate the device label, web interface, or documentation to determine if the system is an ABB ASPECT Enterprise (Ent 12, Ent 2, Ent 256, Ent 96) or ABB Nexus (2128, 2128 A, 2128 F, 2128 G) model.Affected if The device is one of these specific models.
-
Check the firmware versionAccess the device's web interface, administrative console, or use the vendor-provided management tool to retrieve the installed firmware version. Compare it against the version number.Affected if The firmware version is lower than 3.08.03.
-
Locate the file upload functionalityExamine the web application's available features, administrative panels, or configuration menus to identify if a file upload capability exists (often found in settings, configuration, or data import sections).Affected if A file upload feature is present and accessible.
-
Inspect the file upload configurationReview the web server configuration, application settings, or system configuration files to determine what file type validation is applied to uploads (check for whitelist filtering, content inspection, or file type restrictions).Affected if No restrictive file type validation is configured, or the upload accepts script file extensions (.asp, .aspx, .php, .js, .exe, .bat, .sh, etc.).
-
Verify upload directory placementCheck where uploaded files are stored relative to the web root directory, either through configuration inspection or by attempting a safe test upload if authorized.Affected if Uploaded files are stored within the web-accessible directory structure.
The system is affected if it is an ABB ASPECT Enterprise or NEXUS device running firmware version lower than 3.08.03 with an exposed, unrestricted file upload feature.
Generated from the published advisory. Verify against your own configuration.
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 · scoped3.08.03
Implement strict file upload validation including whitelist-based file type checking, content inspection, file renaming, and storage outside web root. Contact ABB for available patches and consider network segmentation to limit exposure.
Firmware version 3.08.03
- Verify current firmware version on the affected device via administrative interface or device status page
- Download firmware version 3.08.03 or later from the official ABB software portal at search.abb.com
- Review ABB upgrade documentation for your specific device model (Aspect Enterprise or Nexus series)
- Create a backup of current device configuration before proceeding with firmware upgrade
- Upload and apply firmware version 3.08.03 through the device's firmware update mechanism
- Verify successful installation by checking the new firmware version in the device administrative interface
- Confirm the unrestricted file upload vulnerability is remediated by validating file upload restrictions are enforced
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
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 locallyCheck whether your project pulls in CVE-2024-51548 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-51548 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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