# CVE-2023-45793: Missing authorization in Siveillance Control

> A local user can gain write privileges for objects they should only read due to improper access group checks in Siemens Siveillance Control.

- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Mar 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-4qph-whwp-xm7r

## What is CVE-2023-45793?

CVE-2023-45793 is a medium-severity missing authorization vulnerability in Siemens Siveillance Control, published on 12 Mar 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability has been identified in Siveillance Control (All versions >= V2.8 < V3.1.1). The affected product does not properly check the list of access groups that are assigned to an individual user. This could enable a locally logged on user to gain write privileges for objects where they only have read privileges.

Weakness: CWE-863 (Incorrect Authorization)

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

It affects 1 product.


Products: Siemens Siveillance Control.

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

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

## Is CVE-2023-45793 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-45793 is a medium-severity missing authorization vulnerability in Siemens Siveillance Control, published on 12 Mar 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-45793 in the wild and no public exploit code.

Affected product: Siemens Siveillance Control. 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-45793/ (Markdown: https://insights.sbomify.com/CVE-2023-45793/index.md)
```

## Sources

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

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