# CVE-2023-5288: Missing authorization in SIM1012

> Remote attackers can access the SIM1012 device without authentication to modify settings, reset the SIM, or upload malicious firmware.

- **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:** 29 Sep 2023
- **Updated:** 9 Dec 2024
- **Also known as:** GHSA-g4x9-h5v7-39wj

## What is CVE-2023-5288?

CVE-2023-5288 is a critical missing authorization vulnerability in SICK AG SIM1012, published on 29 Sep 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A remote unauthorized attacker may connect to the SIM1012, interact with the device and
change configuration settings. The adversary may also reset the SIM and in the worst case upload a
new firmware version to the device.

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Sick Sim1012-0p0g200 Firmware.

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

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

## Is CVE-2023-5288 being exploited?

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

## Other vulnerabilities in SICK AG SIM1012

- [CVE-2022-43990](https://insights.sbomify.com/CVE-2022-43990/): Auth bypass in SICK SIM1012 (high 7.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-5288 is a critical missing authorization vulnerability in SICK AG SIM1012, published on 29 Sep 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-5288 in the wild and no public exploit code.

Affected product: SICK AG SIM1012. 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-5288/ (Markdown: https://insights.sbomify.com/CVE-2023-5288/index.md)
```

## Sources

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

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