# CVE-2024-47407: mySCADA myPRO OS Command Injection

> Unauthenticated remote attackers can inject arbitrary OS commands into mySCADA myPRO Manager due to improper input validation.

- **Severity:** Critical 10.0 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Nov 2024
- **Updated:** 25 Nov 2024
- **Also known as:** GHSA-hc88-rhv5-92jq

## What is CVE-2024-47407?

CVE-2024-47407 is a critical command injection vulnerability in mySCADA myPRO Manager, published on 22 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A parameter within a command does not properly validate input within myPRO Manager which could be exploited by an unauthenticated remote attacker to inject arbitrary operating system commands.

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

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


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

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

## Is CVE-2024-47407 being exploited?

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

Public exploit code:

- mySCADA myPRO Manager Unauthenticated Command Injection (CVE-2024-47407) (metasploit)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-47407 is a critical command injection vulnerability in mySCADA myPRO Manager, published on 22 Nov 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-47407 exists.

Affected product: mySCADA myPRO Manager. 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-47407/ (Markdown: https://insights.sbomify.com/CVE-2024-47407/index.md)
```

## Sources

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

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