Sinumerik 840d Sl vulnerabilitiesRanked by how likely they are to be used.

Product2 versions
The short answer

Sinumerik 840d Sl is made by Siemens. We track 8 published vulnerabilities listed under that exact name, across 2 versions. None of them is on the list of flaws known to be exploited today. Siemens lists newer releases under their own names, such as Sinumerik 840d Sl V4.7, so check those pages too.

See the riskiest flaws

We keep watching the known-exploited list.

Other names

Is Sinumerik 840d Sl listed under other names? Yes.

Siemens also lists Sinumerik 840d Sl under more specific names, such as Sinumerik 840d Sl V4.7 and Sinumerik 840d Sl V4.7 Firmware. Flaws listed only under those names are counted on their own pages, not here. If you run one of these, open its page for its own exploited flaws.

Known exploited

Which Sinumerik 840d Sl vulnerabilities are being exploited?

This is the list that matters most: flaws criminals are using now.

None of Sinumerik 840d Sl's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.

Exploit likelihood

Which Sinumerik 840d Sl flaws are most likely to be used?

Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.

50% or more10% to 49%Under 10%
  1. 3.3%

    Specially crafted packets sent to port 161/udp could cause a denial of service condition.

    CVSS7.5Published26 Dec 2017
  2. 2.1%

    Affected devices improperly handle large amounts of specially crafted UDP packets.

    CVSS7.5Published10 Oct 2019
  3. 1.9%

    A vulnerability has been identified in SINUMERIK 828D V4.7 (All versions < V4.7 SP6 HF1), SINUMERIK 840D sl V4.7 (All versions < V4.7 SP6 HF5), SINUMERIK 840D sl V4.8 (All versions < V4.8 SP3).

    CVSS3.7Published12 Dec 2018
  4. 1.7%

    A vulnerability has been identified in SIMATIC S7-300 CPU family (incl.

    CVSS7.5Published10 Mar 2020
  5. 1.7%

    A vulnerability has been identified in SIMATIC S7-300 CPU family (incl.

    CVSS7.5Published12 Nov 2020
  6. 1.4%

    An attacker with network access to an affected product may cause a denial of service condition by breaking the real-time synchronization (IRT) of the affected installation.

    CVSS7.5Published10 Oct 2019
  7. 1.1%

    Specially crafted PROFINET DCP broadcast packets could cause a denial of service condition of affected products on a local Ethernet segment (Layer 2).

    CVSS6.5Published11 May 2017
  8. 0.9%

    Specially crafted PROFINET DCP packets sent on a local Ethernet segment (Layer 2) to an affected product could cause a denial of service condition of that product.

    CVSS6.5Published11 May 2017
Precursor Intelligence

Running Sinumerik 840d Sl? 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.

Free plan, no card needed. Nothing to install.

FAQ

Common questions, answered plainly.

Something else? Talk to the team →

We track 8 published vulnerabilities listed under the name Sinumerik 840d Sl, across 2 versions.

None of Sinumerik 840d Sl's vulnerabilities is on the list of flaws known to be exploited today.

Siemens also lists Sinumerik 840d Sl under more specific names, such as Sinumerik 840d Sl V4.7 and Sinumerik 840d Sl V4.7 Firmware. Flaws listed only under those names are counted on their own pages, not here. Open the release you run to see its own list.

Create a Precursor Intelligence account and track Sinumerik 840d Sl. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.