# CVE-2022-25751: Other in SCALANCE X302-7 EEC (230V) > Improper input validation in Siemens SCALANCE switches allows attackers to cause a denial of service condition. - **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:** 12 Apr 2022 - **Updated:** 3 Aug 2024 - **Also known as:** GHSA-qcmj-54xw-47h8 ## What is CVE-2022-25751? CVE-2022-25751 is a high-severity vulnerability in Siemens SCALANCE X302-7 EEC (230V), published on 12 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description A vulnerability has been identified in SCALANCE X302-7 EEC (230V), SCALANCE X302-7 EEC (230V, coated), SCALANCE X302-7 EEC (24V), SCALANCE X302-7 EEC (24V, coated), SCALANCE X302-7 EEC (2x 230V), SCALANCE X302-7 EEC (2x 230V, coated), SCALANCE X302-7 EEC (2x 24V), SCALANCE X302-7 EEC (2x 24V, coated), SCALANCE X304-2FE, SCALANCE X306-1LD FE, SCALANCE X307-2 EEC (230V), SCALANCE X307-2 EEC (230V, coated), SCALANCE X307-2 EEC (24V), SCALANCE X307-2 EEC (24V, coated), SCALANCE X307-2 EEC (2x 230V), SCALANCE X307-2 EEC (2x 230V, coated), SCALANCE X307-2 EEC (2x 24V), SCALANCE X307-2 EEC (2x 24V, coated), SCALANCE X307-3, SCALANCE X307-3, SCALANCE X307-3LD, SCALANCE X307-3LD, SCALANCE X308-2, SCALANCE X308-2, SCALANCE X308-2LD, SCALANCE X308-2LD, SCALANCE X308-2LH, SCALANCE X308-2LH, SCALANCE X308-2LH+, SCALANCE X308-2LH+, SCALANCE X308-2M, SCALANCE X308-2M, SCALANCE X308-2M PoE, SCALANCE X308-2M PoE, SCALANCE X308-2M TS, SCALANCE X308-2M TS, SCALANCE X310, SCALANCE X310, SCALANCE X310FE, SCALANCE X310FE, SCALANCE X320-1 FE, SCALANCE X320-1-2LD FE, SCALANCE X408-2, SCALANCE XR324-12M (230V, ports on front), SCALANCE XR324-12M (230V, ports on front), SCALANCE XR324-12M (230V, ports on rear), SCALANCE XR324-12M (230V, ports on rear), SCALANCE XR324-12M (24V, ports on front), SCALANCE XR324-12M (24V, ports on front), SCALANCE XR324-12M (24V, ports on rear), SCALANCE XR324-12M (24V, ports on rear), SCALANCE XR324-12M TS (24V), SCALANCE XR324-12M TS (24V), SCALANCE XR324-4M EEC (100-240VAC/60-250VDC, ports on front), SCALANCE XR324-4M EEC (100-240VAC/60-250VDC, ports on front), SCALANCE XR324-4M EEC (100-240VAC/60-250VDC, ports on rear), SCALANCE XR324-4M EEC (100-240VAC/60-250VDC, ports on rear), SCALANCE XR324-4M EEC (24V, ports on front), SCALANCE XR324-4M EEC (24V, ports on front), SCALANCE XR324-4M EEC (24V, ports on rear), SCALANCE XR324-4M EEC (24V, ports on rear), SCALANCE XR324-4M EEC (2x 100-240VAC/60-250VDC, ports on front), SCALANCE XR324-4M EEC (2x 100-240VAC/60-250VDC, ports on front), SCALANCE XR324-4M EEC (2x 100-240VAC/60-250VDC, ports on rear), SCALANCE XR324-4M EEC (2x 100-240VAC/60-250VDC, ports on rear), SCALANCE XR324-4M EEC (2x 24V, ports on front), SCALANCE XR324-4M EEC (2x 24V, ports on front), SCALANCE XR324-4M EEC (2x 24V, ports on rear), SCALANCE XR324-4M EEC (2x 24V, ports on rear), SCALANCE XR324-4M PoE (230V, ports on front), SCALANCE XR324-4M PoE (230V, ports on rear), SCALANCE XR324-4M PoE (24V, ports on front), SCALANCE XR324-4M PoE (24V, ports on rear), SCALANCE XR324-4M PoE TS (24V, ports on front), SIPLUS NET SCALANCE X308-2. Affected devices do not properly validate the HTTP headers of incoming requests. This could allow an unauthenticated remote attacker to crash affected devices. Weakness: CWE-20 (Improper Input Validation) ## Which versions are affected by CVE-2022-25751? It affects 24 products. Products: Siemens Scalance X302-7eec Firmware, Siemens Scalance X304-2fe Firmware, Siemens Scalance X306-1ldfe Firmware, Siemens Scalance X307-2eec Firmware, Siemens Scalance X307-3 Firmware, Siemens Scalance X307-3ld Firmware, Siemens Scalance X308-2 Firmware, Siemens Scalance X308-2ld Firmware, Siemens Scalance X308-2lh\+ Firmware, Siemens Scalance X308-2lh Firmware, Siemens Scalance X308-2m Firmware, Siemens Scalance X308-2m Poe Firmware, Siemens Scalance X308-2m Ts Firmware, Siemens Scalance X310 Firmware, Siemens Scalance X310fe Firmware, Siemens Scalance X320-1-2ldfe Firmware, Siemens Scalance X320-1fe Firmware, Siemens Scalance X408-2 Firmware, Siemens Scalance Xr324-12m Firmware, Siemens Scalance Xr324-12m Ts Firmware and 4 more. ## How do I fix CVE-2022-25751? No fix has been published for CVE-2022-25751 yet. Limit exposure of the affected software until one is available. ## Is CVE-2022-25751 being exploited? There is no known exploitation of CVE-2022-25751 in the wild and no public exploit code. ## Other vulnerabilities in Siemens SCALANCE X302-7 EEC (230V) - [CVE-2022-25752](https://insights.sbomify.com/CVE-2022-25752/): Weak cryptography in SCALANCE X302-7 EEC (230V) (critical 9.8) - [CVE-2022-25753](https://insights.sbomify.com/CVE-2022-25753/): Memory corruption in SCALANCE X302-7 EEC (230V) (high 8.8) - [CVE-2022-25754](https://insights.sbomify.com/CVE-2022-25754/): Cross-site request forgery in SCALANCE X302-7 EEC (230V) (high 8.8) - [CVE-2022-25755](https://insights.sbomify.com/CVE-2022-25755/): Missing authorization in SCALANCE X302-7 EEC (230V) (high 7.5) - [CVE-2022-26334](https://insights.sbomify.com/CVE-2022-26334/): Memory corruption in SCALANCE X302-7 EEC (230V) (high 7.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2022-25751 and fix it if it is affected. What it is: CVE-2022-25751 is a high-severity vulnerability in Siemens SCALANCE X302-7 EEC (230V), published on 12 Apr 2022. 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-2022-25751 in the wild and no public exploit code. Affected product: Siemens SCALANCE X302-7 EEC (230V). 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-25751/ (Markdown: https://insights.sbomify.com/CVE-2022-25751/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2022-25751 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-25751 - OSV: https://osv.dev/vulnerability/CVE-2022-25751 --- From sbomify Insights: https://insights.sbomify.com/CVE-2022-25751/ Summaries are generated and may contain mistakes; the official description above is the record.