# CVE-2024-48841: Remote Code Execution (RCE) Vulnerabilities

> Remote attackers can execute arbitrary code with elevated privileges on ABB FLXEON devices via network access.

- **Severity:** Critical 10.0 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Jan 2025
- **Updated:** 14 Feb 2025
- **Also known as:** GHSA-v9p4-62pm-466x

## What is CVE-2024-48841?

CVE-2024-48841 is a critical command injection vulnerability in ABB FLXEON, published on 27 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Network access can be used to execute arbitrary code with elevated privileges. 

This
issue affects FLXEON 9.3.4 and older.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

## Which versions are affected by CVE-2024-48841?


## How do I fix CVE-2024-48841?

No fix has been published for CVE-2024-48841 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-48841 being exploited?

There is no known exploitation of CVE-2024-48841 in the wild and no public exploit code.

Public exploit code:

- ABB Cylon FLXeon 9.3.4 - Remote Code Execution (RCE) (exploitdb)
- ABB Cylon FLXeon 9.3.4 - Remote Code Execution (Authenticated) (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-48841 and fix it if it is affected.

What it is: CVE-2024-48841 is a critical command injection vulnerability in ABB FLXEON, published on 27 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-48841 in the wild and no public exploit code.

Affected product: ABB FLXEON. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-48841/ (Markdown: https://insights.sbomify.com/CVE-2024-48841/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-48841
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-48841
- OSV: https://osv.dev/vulnerability/CVE-2024-48841

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-48841/
Summaries are generated and may contain mistakes; the official description above is the record.