# CVE-2023-46281: Other in Opcenter Execution Foundation

> An overly permissive CORS policy in Siemens UMC Web-UI allows attackers to trick users into triggering unwanted behavior.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:L/E:P/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 12 Dec 2023
- **Updated:** 14 Jan 2025
- **Also known as:** GHSA-9qvw-gvq6-g569

## What is CVE-2023-46281?

CVE-2023-46281 is a high-severity vulnerability in Siemens Opcenter Execution Foundation, published on 12 Dec 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A vulnerability has been identified in Opcenter Execution Foundation (All versions < V2407), Opcenter Quality (All versions < V2312), SIMATIC PCS neo (All versions < V4.1), SINEC NMS (All versions < V2.0 SP1), Totally Integrated Automation Portal (TIA Portal) V14 (All versions), Totally Integrated Automation Portal (TIA Portal) V15.1 (All versions), Totally Integrated Automation Portal (TIA Portal) V16 (All versions), Totally Integrated Automation Portal (TIA Portal) V17 (All versions < V17 Update 8), Totally Integrated Automation Portal (TIA Portal) V18 (All versions < V18 Update 3). When accessing the UMC Web-UI from affected products, UMC uses an overly permissive CORS policy. This could allow an attacker to trick a legitimate user to trigger unwanted behavior.

Weakness: CWE-942 (Permissive Cross-domain Security Policy with Untrusted Domains)

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

It affects 4 products.


Products: Siemens Opcenter Quality, Siemens Simatic Pcs Neo, Siemens Sinumerik Integrate Runmyhmi \/Automotive, Siemens Totally Integrated Automation Portal.

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

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

## Is CVE-2023-46281 being exploited?

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

## Other vulnerabilities in Siemens Opcenter Execution Foundation

- [CVE-2021-27389](https://insights.sbomify.com/CVE-2021-27389/): Hardcoded credentials in Opcenter Quality (critical 9.8)
- [CVE-2024-41979](https://insights.sbomify.com/CVE-2024-41979/): Missing authorization in SOA Audit (high 7.5)
- [CVE-2023-46283](https://insights.sbomify.com/CVE-2023-46283/): Memory corruption in Opcenter Execution Foundation (high 7.5)
- [CVE-2023-46284](https://insights.sbomify.com/CVE-2023-46284/): Memory corruption in Opcenter Execution Foundation (high 7.5)
- [CVE-2023-46285](https://insights.sbomify.com/CVE-2023-46285/): Denial of service in Opcenter Execution Foundation (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-46281 is a high-severity vulnerability in Siemens Opcenter Execution Foundation, published on 12 Dec 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-46281 in the wild and no public exploit code.

Affected product: Siemens Opcenter Execution Foundation. 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-46281/ (Markdown: https://insights.sbomify.com/CVE-2023-46281/index.md)
```

## Sources

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

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