# CVE-2024-51721: Vulnerabilities in SecuSUITE Server Components Impact SecuSUITE

> Attackers can inject executable content into the SecuSUITE Server Web Administration Portal to run commands with root privileges.

- **Severity:** High 7.3 (`CVSS:3.1/AV:A/AC:H/PR:H/UI:R/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 12 Nov 2024
- **Updated:** 12 Nov 2024
- **Also known as:** GHSA-rp64-jc8m-27wc

## What is CVE-2024-51721?

CVE-2024-51721 is a high-severity code injection vulnerability in BlackBerry SecuSUITE, published on 12 Nov 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A code injection vulnerability in the SecuSUITE Server Web Administration Portal of SecuSUITE versions 5.0.420 and earlier could allow an attacker to potentially inject script commands or other executable content into the server that would run with root privilege.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

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


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

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

## Is CVE-2024-51721 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-51721 is a high-severity code injection vulnerability in BlackBerry SecuSUITE, published on 12 Nov 2024. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-51721 in the wild and no public exploit code.

Affected product: BlackBerry SecuSUITE. 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-51721/ (Markdown: https://insights.sbomify.com/CVE-2024-51721/index.md)
```

## Sources

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

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