# CVE-2023-23452: Missing authorization in FX0-GPNT v3 Firmware

> Unauthenticated remote attackers can execute arbitrary code on SICK FX0-GPNT devices by sending malicious RK512 commands to TCP port 9000.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Feb 2023
- **Updated:** 18 Mar 2025
- **Also known as:** GHSA-c93f-7869-prcf

## What is CVE-2023-23452?

CVE-2023-23452 is a critical missing authorization vulnerability in FX0-GPNT v3 Firmware, published on 20 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Missing Authentication for Critical Function in SICK FX0-GPNT v3 Firmware Version V3.04 and V3.05 allows an unprivileged remote attacker to achieve arbitrary remote code execution via maliciously crafted RK512 commands to the listener on TCP port 9000.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2023-23452?

It affects 2 products.


Products: Sick Fx0-Gpnt00000 Firmware, Sick Fx0-Gpnt00010 Firmware.

## How do I fix CVE-2023-23452?

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

## Is CVE-2023-23452 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-23452 and fix it if it is affected.

What it is: CVE-2023-23452 is a critical missing authorization vulnerability in FX0-GPNT v3 Firmware, published on 20 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-23452 in the wild and no public exploit code.

Affected product: FX0-GPNT v3 Firmware. 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-2023-23452/ (Markdown: https://insights.sbomify.com/CVE-2023-23452/index.md)
```

## Sources

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

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