# CVE-2024-48904: Command injection in Trend Micro Cloud Edge

> Remote attackers can execute arbitrary code on Trend Micro Cloud Edge appliances without authentication due to a command injection flaw.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Oct 2024
- **Updated:** 22 Oct 2024
- **Also known as:** GHSA-mh56-hmf5-hg22

## What is CVE-2024-48904?

CVE-2024-48904 is a critical command injection vulnerability in Trend Micro Cloud Edge, published on 22 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An command injection vulnerability in Trend Micro Cloud Edge could allow a remote attacker to execute arbitrary code on affected appliances.

Please note: authentication is not required in order to exploit this vulnerability.

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

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

It affects 1 product.


Products: Trendmicro Cloud Edge.

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

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

## Is CVE-2024-48904 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-48904 is a critical command injection vulnerability in Trend Micro Cloud Edge, published on 22 Oct 2024. 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-48904 in the wild and no public exploit code.

Affected product: Trend Micro Cloud Edge. 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-48904/ (Markdown: https://insights.sbomify.com/CVE-2024-48904/index.md)
```

## Sources

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

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