# CVE-2022-46144: Denial of service in SCALANCE SC622-2C

> An authenticated attacker can cause a denial of service on the CLI interface by forcefully quitting an SSH connection.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **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:** 13 Dec 2022
- **Updated:** 21 Apr 2025
- **Also known as:** GHSA-p939-r66p-8wwm

## What is CVE-2022-46144?

CVE-2022-46144 is a high-severity denial of service vulnerability in Siemens SCALANCE SC622-2C, published on 13 Dec 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 SCALANCE SC622-2C (6GK5622-2GS00-2AC2) (All versions < V2.3), SCALANCE SC622-2C (6GK5622-2GS00-2AC2) (All versions >= V2.3 < V3.0), SCALANCE SC626-2C (6GK5626-2GS00-2AC2) (All versions < V2.3), SCALANCE SC626-2C (6GK5626-2GS00-2AC2) (All versions >= V2.3 < V3.0), SCALANCE SC632-2C (6GK5632-2GS00-2AC2) (All versions < V2.3), SCALANCE SC632-2C (6GK5632-2GS00-2AC2) (All versions >= V2.3 < V3.0), SCALANCE SC636-2C (6GK5636-2GS00-2AC2) (All versions < V2.3), SCALANCE SC636-2C (6GK5636-2GS00-2AC2) (All versions >= V2.3 < V3.0), SCALANCE SC642-2C (6GK5642-2GS00-2AC2) (All versions < V2.3), SCALANCE SC642-2C (6GK5642-2GS00-2AC2) (All versions >= V2.3 < V3.0), SCALANCE SC646-2C (6GK5646-2GS00-2AC2) (All versions < V2.3), SCALANCE SC646-2C (6GK5646-2GS00-2AC2) (All versions >= V2.3 < V3.0), SCALANCE WAM763-1 (6GK5763-1AL00-7DA0) (All versions < V2.0.0), SCALANCE WAM766-1 (6GK5766-1GE00-7DA0) (All versions < V2.0.0), SCALANCE WAM766-1 (US) (6GK5766-1GE00-7DB0) (All versions < V2.0.0), SCALANCE WAM766-1 EEC (6GK5766-1GE00-7TA0) (All versions < V2.0.0), SCALANCE WAM766-1 EEC (US) (6GK5766-1GE00-7TB0) (All versions < V2.0.0), SCALANCE WUM763-1 (6GK5763-1AL00-3AA0) (All versions < V2.0.0), SCALANCE WUM763-1 (6GK5763-1AL00-3DA0) (All versions < V2.0.0), SCALANCE WUM766-1 (6GK5766-1GE00-3DA0) (All versions < V2.0.0), SCALANCE WUM766-1 (USA) (6GK5766-1GE00-3DB0) (All versions < V2.0.0). Affected devices do not properly process CLI commands after a user forcefully quitted the SSH connection. This could allow an authenticated attacker to make the CLI via SSH or serial  interface irresponsive.

Weakness: CWE-664 (Improper Control of a Resource Through its Lifetime)

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

It affects 6 products.


Products: Siemens 6gk5622-2gs00-2ac2 Firmware, Siemens 6gk5626-2gs00-2ac2 Firmware, Siemens 6gk5632-2gs00-2ac2 Firmware, Siemens 6gk5636-2gs00-2ac2 Firmware, Siemens 6gk5642-2gs00-2ac2 Firmware, Siemens 6gk5646-2gs00-2ac2 Firmware.

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

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

## Is CVE-2022-46144 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-46144 is a high-severity denial of service vulnerability in Siemens SCALANCE SC622-2C, published on 13 Dec 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-46144 in the wild and no public exploit code.

Affected product: Siemens SCALANCE SC622-2C. 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-46144/ (Markdown: https://insights.sbomify.com/CVE-2022-46144/index.md)
```

## Sources

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

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