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

> Attackers can execute arbitrary commands as root on Wi-Fi Alliance test suite devices via crafted 802.11x frames due to unsafe system() usage.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Nov 2024
- **Updated:** 12 Nov 2024
- **Also known as:** GHSA-xwr3-f5gh-9v6w

## What is CVE-2024-41992?

CVE-2024-41992 is a high-severity command injection vulnerability in n/a, published on 11 Nov 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Wi-Fi Alliance wfa_dut (in Wi-Fi Test Suite) through 9.0.0 allows OS command injection via 802.11x frames because the system() library function is used. For example, on Arcadyan FMIMG51AX000J devices, this leads to wfaTGSendPing remote code execution as root via traffic to TCP port 8000 or 8080 on a LAN interface. On other devices, this may be exploitable over a WAN interface.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


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

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

## Is CVE-2024-41992 being exploited?

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

Public exploit code:

- PoC for the CVE-2024-41992 (RCE on devices running WiFi-TestSuite-DUT) (github_poc): https://github.com/fj016/CVE-2024-41992-PoC

## Fix prompt for AI coding agents

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

What it is: CVE-2024-41992 is a high-severity command injection vulnerability in n/a, published on 11 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-41992 in the wild and no public exploit code.

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-41992/ (Markdown: https://insights.sbomify.com/CVE-2024-41992/index.md)
```

## Sources

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

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