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

> Local attackers with system account control can escalate privileges to execute privileged script commands in SecuSUITE Server.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/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:** Not needed
- **Fix available:** No
- **Published:** 12 Nov 2024
- **Updated:** 13 Nov 2024
- **Also known as:** GHSA-ggrr-222r-c74p

## What is CVE-2024-51722?

CVE-2024-51722 is a medium-severity vulnerability in BlackBerry SecuSUITE, published on 12 Nov 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A local privilege escalation vulnerability in the SecuSUITE Server (System Configuration) of SecuSUITE versions 5.0.420 and earlier could allow a successful attacker that had gained control of code running under one of the system accounts listed in the configuration file to potentially issue privileged script commands.

Weakness: CWE-250 (Execution with Unnecessary Privileges)

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


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

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

## Is CVE-2024-51722 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-51722 is a medium-severity vulnerability in BlackBerry SecuSUITE, published on 12 Nov 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-51722 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-51722/ (Markdown: https://insights.sbomify.com/CVE-2024-51722/index.md)
```

## Sources

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

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