dbcve.org
Scalance X300 FirmwareOperating system · Siemens

CVE-2018-4848

MEDIUM · 6.1 CVSS v3.0 Published 2018-06-14
Fix available
A fix is available. Upgrade to 5.2.3 / 5.4.1 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 X-200 switch family (incl. SIPLUS NET variants) (All versions < V5.2.3), SCALANCE X-200IRT switch family (incl. SIPLUS NET variants) (All versions < V5.4.1), SCALANCE X-200RNA switch family (All versions < V3.2.7), SCALANCE X-300 switch family (incl. X408 and SIPLUS NET variants) (All versions < V4.1.3). The integrated configuration web server of the affected devices could allow Cross-Site Scripting (XSS) attacks if unsuspecting users are tricked into accessing a malicious link. User interaction is required for a successful exploitation. The user must be logged into the web interface in order for the exploitation to succeed. At the stage of publishing this security advisory no public exploitation is known. The vendor has confirmed the vulnerability and provides mitigations to resolve it.

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 the integrated configuration web server of Siemens SCALANCE X-200, X-200IRT, X-200RNA, and X-300 switch families. An attacker can inject malicious JavaScript via a crafted URL that gets executed in the context of a logged-in user's browser session.

MitigationUpdate affected devices to firmware versions V5.2.3 or higher (X-200), V5.4.1 or higher (X-200IRT), V3.2.7 or higher (X-200RNA), or V4.1.3 or higher (X-300). Users should avoid clicking untrusted links while authenticated to the web interface.

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 X300 FirmwareOperating system
Affected:all versions
Scalance X 200 Irt FirmwareOperating system
Affected:< 5.4.1
Scalance X 200 FirmwareHardware / appliance
Affected:< 5.2.3

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.0/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 the SCALANCE device model
    Access the web interface login page or check the device label/console output to confirm the exact model (X-200, X-200IRT, X-200RNA, or X-300)
    Affected if The model is one of the four affected families listed in the CVE
  2. Determine the installed firmware version
    Log into the web configuration interface and navigate to the firmware or system information page (typically under System > Info or Device Information). The firmware version is displayed there.
    Affected if The firmware version cannot be determined or is visible but the model is affected
  3. Compare firmware version against affected ranges
    Cross-reference the identified firmware version with these ranges: X-200 < 5.2.3 is affected, X-200IRT < 5.4.1 is affected, X-300 all versions are affected, X-200RNA check V3.2.7 as reference
    Affected if For X-200: version is below 5.2.3; for X-200IRT: version is below 5.4.1; for X-300: any version; for X-200RNA: version is below 3.2.7 (reference)
  4. Verify web server is enabled
    Confirm the integrated configuration web server is accessible and active on the device (default on ports 80/443). This is required for the XSS to be exploitable.
    Affected if The web server interface is accessible and the device is on the network with web management enabled

The device is affected if it is a SCALANCE X-200 (firmware < 5.2.3), X-200IRT (firmware < 5.4.1), X-200RNA (firmware < 3.2.7), or X-300 (any version) and the web management interface is enabled and accessible.

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.

From vendor data
Upgrade available Upgrade to 5.2.3 / 5.4.1 or later
Fixed in 5.2.35.4.1
Interim mitigation

Update affected devices to firmware versions V5.2.3 or higher (X-200), V5.4.1 or higher (X-200IRT), V3.2.7 or higher (X-200RNA), or V4.1.3 or higher (X-300). Users should avoid clicking untrusted links while authenticated to the web interface.

Fix this in Scalance X300 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-2018-4848 — 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-2018-4848 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