dbcve.org
Scalance X200 4p Irt FirmwareOperating system · Siemens

CVE-2022-40631

MEDIUM · 6.1 CVSS v3.1 Published 2022-10-11
Fix available
A fix is available. Upgrade to 5.2.5 / 5.5.0 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability has been identified in SCALANCE X200-4P IRT (All versions < V5.5.0), SCALANCE X201-3P IRT (All versions < V5.5.0), SCALANCE X201-3P IRT PRO (All versions < V5.5.0), SCALANCE X202-2IRT (All versions < V5.5.0), SCALANCE X202-2P IRT (All versions < V5.5.0), SCALANCE X202-2P IRT PRO (All versions < V5.5.0), SCALANCE X204-2 (All versions < V5.2.5), SCALANCE X204-2FM (All versions < V5.2.5), SCALANCE X204-2LD (All versions < V5.2.5), SCALANCE X204-2LD TS (All versions < V5.2.5), SCALANCE X204-2TS (All versions < V5.2.5), SCALANCE X204IRT (All versions < V5.5.0), SCALANCE X204IRT PRO (All versions < V5.5.0), SCALANCE X206-1 (All versions < V5.2.5), SCALANCE X206-1LD (All versions < V5.2.5), SCALANCE X208 (All versions < V5.2.5), SCALANCE X208PRO (All versions < V5.2.5), SCALANCE X212-2 (All versions < V5.2.5), SCALANCE X212-2LD (All versions < V5.2.5), SCALANCE X216 (All versions < V5.2.5), SCALANCE X224 (All versions < V5.2.5), SCALANCE XF201-3P IRT (All versions < V5.5.0), SCALANCE XF202-2P IRT (All versions < V5.5.0), SCALANCE XF204 (All versions < V5.2.5), SCALANCE XF204-2 (All versions < V5.2.5), SCALANCE XF204-2BA IRT (All versions < V5.5.0), SCALANCE XF204IRT (All versions < V5.5.0), SCALANCE XF206-1 (All versions < V5.2.5), SCALANCE XF208 (All versions < V5.2.5), SIPLUS NET SCALANCE X202-2P IRT (All versions < V5.5.0). There is a cross-site scripting vulnerability on the affected devices, that if used by a threat actor, it could result in session hijacking.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Cross-site scripting (XSS) vulnerability in SCALANCE X series industrial network switches (multiple models) allows remote attackers to inject malicious scripts through the web interface. Successful exploitation can lead to session hijacking via stolen session cookies or credentials.

MitigationUpdate affected devices to firmware version V5.5.0 (for IRT models) or V5.2.5 (for other models). If patching is not immediately feasible, restrict web interface access to trusted networks only and disable HTTP/HTTPS management if not required.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Scalance X200 4p Irt FirmwareOperating system
Affected:< 5.5.0
Scalance X201 3p Irt FirmwareOperating system
Affected:< 5.5.0
Scalance X201 3p Irt Pro FirmwareOperating system
Affected:< 5.5.0
Scalance X202 2irt FirmwareOperating system
Affected:< 5.5.0
Scalance X202 2p Irt FirmwareOperating system
Affected:< 5.5.0
Scalance X202 2p Irt Pro FirmwareOperating system
Affected:< 5.5.0
Scalance X204 2 FirmwareOperating system
Affected:< 5.2.5
Scalance X204 2fm FirmwareOperating system
Affected:< 5.2.5

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify SCALANCE X model
    Access the device web interface, use SNMP, or check the physical device label to determine the exact model (e.g., X200 4p Irt, X201 3p Irt, X202 2irt, X204 2, X204 2fm)
    Affected if The model matches one of the affected products listed in the CVE
  2. Check installed firmware version
    Log into the device web interface and navigate to System > Firmware or use CLI command 'show firmware version' to determine the installed firmware version
    Affected if The firmware version is below 5.5.0 for IRT models (X200 4p Irt, X201 3p Irt, X201 3p Irt Pro, X202 2irt, X202 2p Irt, X202 2p Irt Pro) or below 5.2.5 for non-IRT models (X204 2, X204 2fm)
  3. Verify web interface is enabled
    Check device configuration via web interface under Administration > HTTP/HTTPS settings, or via CLI with 'show ip http' or 'show ip https' command to confirm web management is active
    Affected if HTTP or HTTPS web interface management is enabled on the device

Device is affected if it is a SCALANCE X model listed in the CVE, runs firmware below the threshold (5.5.0 for IRT models or 5.2.5 for others), and has the web interface enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 5.2.5 / 5.5.0 or later
Fixed in 5.2.55.5.0
Interim mitigation

Update affected devices to firmware version V5.5.0 (for IRT models) or V5.2.5 (for other models). If patching is not immediately feasible, restrict web interface access to trusted networks only and disable HTTP/HTTPS management if not required.

Recommended fix High confidence

V5.5.0 for X200/X201/X202/X204IRT/XF201/XF202/XF204IRT models; V5.2.5 for X204-2/X206-1/X208/X212/X216/X224/XF204/XF206-1/XF208 models

  1. Identify the specific SCALANCE X model in your environment from the list of affected products
  2. Check the current firmware version of the affected device through the web interface or management console
  3. Download the appropriate firmware update from Siemens Industry Online Support (support.industry.siemens.com) using the product-specific entry
  4. For models X200-4P IRT, X201-3P IRT, X201-3P IRT PRO, X202-2IRT, X202-2P IRT, X202-2P IRT PRO, X204IRT, X204IRT PRO, XF201-3P IRT, XF202-2P IRT, XF204-2BA IRT, XF204IRT, and SIPLUS NET SCALANCE X202-2P IRT: upgrade to firmware V5.5.0 or later
  5. For models X204-2, X204-2FM, X204-2LD, X204-2LD TS, X204-2TS, X206-1, X206-1LD, X208, X208PRO, X212-2, X212-2LD, X216, X224, XF204, XF204-2, XF206-1, XF208: upgrade to firmware V5.2.5 or later
  6. Upload and install the firmware via the device web interface or management tool following Siemens upgrade instructions
  7. After upgrading, verify the firmware version in the device web interface to confirm the update was successful
  8. Test device functionality to ensure normal operation after the firmware update

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Scalance X200 4p Irt Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-40631 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-40631 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data