# CVE-2024-7059: Code injection in Genetec Security Center

> Attackers can execute arbitrary code on the system hosting the Web SDK role in Genetec Security Center.

- **Severity:** High 8.9 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Nov 2024
- **Updated:** 9 Nov 2024
- **Also known as:** GHSA-h4jp-rw7w-8x59

## What is CVE-2024-7059?

CVE-2024-7059 is a high-severity code injection vulnerability in Genetec Security Center, published on 5 Nov 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A high-severity vulnerability that can lead to arbitrary code execution on the system hosting the Web SDK role was found in the Genetec Security Center product line.

Weakness: CWE-470 (Use of Externally-Controlled Input to Select Classes or Code)

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


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

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

## Is CVE-2024-7059 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-7059 is a high-severity code injection vulnerability in Genetec Security Center, published on 5 Nov 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-7059 in the wild and no public exploit code.

Affected product: Genetec Security Center. 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-7059/ (Markdown: https://insights.sbomify.com/CVE-2024-7059/index.md)
```

## Sources

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

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