# CVE-2024-10771: SICK InspectorP61x, SICK InspectorP62x and SICK TiM3xx are vulnerable for remote code execution

> Attackers with Service-level network access can execute arbitrary root commands via missing input validation during firmware updates on SICK industrial devices.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Dec 2024
- **Updated:** 13 May 2026
- **Also known as:** GHSA-252q-qph8-r7q3

## What is CVE-2024-10771?

CVE-2024-10771 is a high-severity code injection vulnerability in SICK InspectorP61x, published on 6 Dec 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Due to missing input validation during one step of the firmware update process, the product
is vulnerable to remote code execution. With network access and the user level ”Service”, an attacker
can execute arbitrary system commands in the root user’s contexts.

Weakness: CWE-94 (Improper Control of Generation of Code)

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


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

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

## Is CVE-2024-10771 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-10771 is a high-severity code injection vulnerability in SICK InspectorP61x, published on 6 Dec 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-10771 in the wild and no public exploit code.

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

## Sources

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

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