Sign inStart freeBook a demo

What is CVE-2018-4848?A medium-severity flaw in Scalance X-200, explained.

Medium severity6 affected products
The short answer

CVE-2018-4848 is a medium-severity flaw (CVSS 6.1) in Scalance X-200 from Siemens, published on 14 June 2018. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 1.0%. If you run an affected version, plan in the vendor’s fix.

Check if it affects you →How to fix it

Published 14 June 2018. Record last updated 13 December 2022. We keep this page's data up to date.

What it does

What is CVE-2018-4848? In plain terms.

It can be attacked from anywhere on the internet without logging in, but a person has to take an action first. If it works, the attacker can read some data and change some data.

The official description

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.

What kind of flaw is it?

  • CWE-79Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
  • CWE-80Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS)
CVSS 3.0 scoreMedium · 6.1

How an attack on it works

Read straight from its severity rating, translated out of the shorthand.

  • Where an attacker can beAnywhere on the internet
  • How hard it is to pull offEasy: no special conditions
  • Login needed firstNo login needed
  • Does someone have to clickYes, a person has to take an action
  • What an attacker getsCan read some data and change some data

Severity vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Exploitation

Is CVE-2018-4848 being exploited? Not that we know of.

It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 1.0%. That can change at any time, which is why we keep watching.

Known to be exploitedNoNot on the list of exploited flaws today
Chance of use in the next 30 days1.0%Its EPSS score, from the latest forecast

Timeline

  1. Published
  2. Record last updated
How Precursor Intelligence ranks it
23out of 100Low

CVE-2018-4848 scores 23. Action: Monitor.

We keep the score of every published flaw up to date as the evidence changes. Four things go into the score, and evidence that criminals are actually using it counts most. In order:

  • Evidence it is being exploitedBiggest factor
  • How severe it isStrong factor
  • How widely exposed it isSmaller factor
  • Threat activity around itSmaller factor

85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score.

When CVE-2018-4848 matches software you track, it lands in your list with its score and the reasons behind it.

See your own ranked list →
Affected products

Who is affected by CVE-2018-4848? 6 products.

The published record lists 6 products from 1 vendor. Versions are shown as published: "before 5.2.3" means every version up to, but not including, 5.2.3. If you run one of these, check your version, then go to the fix below.

Remediation

How do I fix CVE-2018-4848? Four steps.

  1. Check whether you run itCompare your versions with the affected products above. Not sure what you run? Precursor Intelligence can work it out from your public website, or you can pick it from a list.
  2. Apply the vendor’s fixInstall the update named in the vendor’s advisory. We’ve put the advisory first in the list.
  3. If you can’t patch todayFollow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
  4. Keep an eye on itTrack the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood.

References

2 links
Precursor Intelligence

Does CVE-2018-4848 affect you? We'll keep checking.

Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.

  1. Tell us what you runPick your software from a list, or let us work it out from your website.
  2. We match it to every flawOver 400,000 published flaws, checked against your list.
  3. Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
  4. Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Start free →Book a demo

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

CVE-2018-4848 is a medium-severity flaw in Scalance X-200 from Siemens, published on 14 June 2018. It can be attacked from anywhere on the internet without logging in, but a person has to take an action first. If it works, the attacker can read some data and change some data.

It scores 6.1 out of 10 on the CVSS severity scale, which is medium. Our risk score for CVE-2018-4848 is 23 out of 100, which is Low. Its action is "Monitor". No sign of exploitation and a low forecast. Patch it in your normal update cycle.

It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 1.0%. That can change at any time, which is why we keep watching.

For Scalance X-200 from Siemens: version not specified. The record lists 6 products in all, each with its versions, under "Who is affected" on this page.

Install the update the vendor names in its advisory, linked first under "How do I fix" on this page. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet.

Keep exploring