# CVE-2022-40182: Code injection in Desigo PXM30-1

> Attackers can inject JavaScript into graphics to exploit the root-level embedded browser, leading to code execution and privilege escalation on Siemens Desigo devices.

- **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:** 11 Oct 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-fjvx-fw48-vr4j

## What is CVE-2022-40182?

CVE-2022-40182 is a high-severity code injection vulnerability in Siemens Desigo PXM30-1, published on 11 Oct 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability has been identified in Desigo PXM30-1 (All versions < V02.20.126.11-41), Desigo PXM30.E (All versions < V02.20.126.11-41), Desigo PXM40-1 (All versions < V02.20.126.11-41), Desigo PXM40.E (All versions < V02.20.126.11-41), Desigo PXM50-1 (All versions < V02.20.126.11-41), Desigo PXM50.E (All versions < V02.20.126.11-41), PXG3.W100-1 (All versions < V02.20.126.11-37), PXG3.W100-2 (All versions < V02.20.126.11-41), PXG3.W200-1 (All versions < V02.20.126.11-37), PXG3.W200-2 (All versions < V02.20.126.11-41). The device embedded Chromium-based browser is launched as root with the “--no-sandbox” option. Attackers can add arbitrary JavaScript code inside “Operation” graphics and successfully exploit any number of publicly known vulnerabilities against the version of the embedded Chromium-based browser.

Weakness: CWE-250 (Execution with Unnecessary Privileges)

## Which versions are affected by CVE-2022-40182?

It affects 10 products.


Products: Siemens Desigo Pxm30-1 Firmware, Siemens Desigo Pxm30.e Firmware, Siemens Desigo Pxm40-1 Firmware, Siemens Desigo Pxm40.e Firmware, Siemens Desigo Pxm50-1 Firmware, Siemens Desigo Pxm50.e Firmware, Siemens Pxg3.w100-1 Firmware, Siemens Pxg3.w100-2 Firmware, Siemens Pxg3.w200-1 Firmware, Siemens Pxg3.w200-2 Firmware.

## How do I fix CVE-2022-40182?

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

## Is CVE-2022-40182 being exploited?

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

## Other vulnerabilities in Siemens Desigo PXM30-1

- [CVE-2022-40181](https://insights.sbomify.com/CVE-2022-40181/): Cross-site scripting in Desigo PXM30-1 (high 8.3)
- [CVE-2022-40179](https://insights.sbomify.com/CVE-2022-40179/): Cross-site request forgery in Desigo PXM30-1 (high 8.1)
- [CVE-2022-40176](https://insights.sbomify.com/CVE-2022-40176/): Command injection in Desigo PXM30-1 (high 8.0)
- [CVE-2022-40177](https://insights.sbomify.com/CVE-2022-40177/): Information disclosure in Desigo PXM30-1 (medium 5.7)
- [CVE-2022-40178](https://insights.sbomify.com/CVE-2022-40178/): Cross-site scripting in Desigo PXM30-1 (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-40182 and fix it if it is affected.

What it is: CVE-2022-40182 is a high-severity code injection vulnerability in Siemens Desigo PXM30-1, published on 11 Oct 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-40182 in the wild and no public exploit code.

Affected product: Siemens Desigo PXM30-1. 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-2022-40182/ (Markdown: https://insights.sbomify.com/CVE-2022-40182/index.md)
```

## Sources

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

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