# CVE-2024-22107: Command injection in n/a

> An authenticated attacker can inject arbitrary commands via the DNS data endpoint in GTB Central Console, leading to platform compromise.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Feb 2024
- **Updated:** 15 May 2025
- **Also known as:** GHSA-r3vw-5726-q8gc

## What is CVE-2024-22107?

CVE-2024-22107 is a high-severity command injection vulnerability in n/a, published on 2 Feb 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

An issue was discovered in GTB Central Console 15.17.1-30814.NG. The method systemSettingsDnsDataAction at /opt/webapp/src/AppBundle/Controller/React/SystemSettingsController.php is vulnerable to command injection via the /old/react/v1/api/system/dns/data endpoint. An authenticated attacker can abuse it to inject an arbitrary command and compromise the platform.

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

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

It affects 1 product.


Products: Gttb Gtb Central Console.

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

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

## Is CVE-2024-22107 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-22107 exists.

## Other vulnerabilities in n/a

- [CVE-2024-22108](https://insights.sbomify.com/CVE-2024-22108/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-22107 is a high-severity command injection vulnerability in n/a, published on 2 Feb 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-22107 exists.

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

## Sources

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

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