# CVE-2025-0592: SICK Lector8xx and InspectorP8xx vulnerable for code execution

> Remote low-privileged attackers can execute arbitrary shell commands on SICK Lector8xx and InspectorP8xx devices by manipulating firmware files.

- **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:** 14 Feb 2025
- **Updated:** 14 Feb 2025
- **Also known as:** GHSA-qx7g-8cqg-c43v

## What is CVE-2025-0592?

CVE-2025-0592 is a high-severity command injection vulnerability in SICK InspectorP8xx, published on 14 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The vulnerability may allow a remote low priviledged attacker to run arbitrary shell commands by manipulating the firmware file and uploading it to the device.

Weakness: CWE-924 (Improper Enforcement of Message Integrity During Transmission in a Communication Channel)

## Which versions are affected by CVE-2025-0592?


## How do I fix CVE-2025-0592?

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

## Is CVE-2025-0592 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-0592 and fix it if it is affected.

What it is: CVE-2025-0592 is a high-severity command injection vulnerability in SICK InspectorP8xx, published on 14 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-0592 in the wild and no public exploit code.

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

## Sources

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

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