Scalance Xc-200 vulnerabilitiesRanked by how likely they are to be used.
Scalance Xc-200 is made by Siemens. We track 12 published vulnerabilities listed under that exact name, across 0 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 Scalance Xc-200 Firmware, so check those pages too.
We keep watching the known-exploited list.
Is Scalance Xc-200 listed under other names? Yes.
Siemens also lists Scalance Xc-200 under more specific names, such as Scalance Xc-200 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.
Which Scalance Xc-200 vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Scalance Xc-200's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Scalance Xc-200 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.
- 64%CVE-2021-3449Medium
An OpenSSL TLS server may crash if sent a maliciously crafted renegotiation ClientHello message from a client.
- 1.9%CVE-2020-28400High
Affected devices contain a vulnerability that allows an unauthenticated attacker to trigger a denial of service condition.
- 1.8%CVE-2022-36323Critical
Affected devices do not properly sanitize an input field.
- 1.7%CVE-2022-36324High
Affected devices do not properly handle the renegotiation of SSL/TLS parameters.
- 1.5%CVE-2019-13946High
Profinet-IO (PNIO) stack versions prior V06.00 do not properly limit internal resource allocation when multiple legitimate diagnostic package requests are sent to the DCE-RPC interface.
- 1.4%CVE-2019-19301High
A vulnerability has been identified in SCALANCE X200-4P IRT, SCALANCE X201-3P IRT, SCALANCE X201-3P IRT PRO, SCALANCE X202-2IRT, SCALANCE X202-2P IRT, SCALANCE X202-2P IRT PRO, SCALANCE X204-2, SCALANCE X204-2FM,...
- 1.3%CVE-2019-6569Critical
The monitor barrier of the affected products insufficiently blocks data from being forwarded over the mirror port into the mirrored network.
- 1.2%CVE-2019-10927Medium
A vulnerability has been identified in SCALANCE SC-600 (V2.0), SCALANCE XB-200 (V4.1), SCALANCE XC-200 (V4.1), SCALANCE XF-200BA (V4.1), SCALANCE XP-200 (V4.1), SCALANCE XR-300WG (V4.1).
- 1.1%CVE-2017-12736High
After initial configuration, the Ruggedcom Discovery Protocol (RCDP) is still able to write to the device under certain conditions.
- 1.0%CVE-2022-36325Medium
Affected devices do not properly sanitize data introduced by an user when rendering the web interface.
Running Scalance Xc-200? 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.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- 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.
1 new flaw affects software Acme tracks
An OpenSSL TLS server may crash if sent a maliciously crafted renegotiation ClientHello message from a client. If a TLSv1.2 renegotiation ClientHello omits the signature_algorithms extension (where it was present in the initial ClientHello), but includes a signature_algorithms_cert extension then a NULL pointer dereference will result, leading to a crash and a denial of service attack. A server is only vulnerable if it has TLSv1.2 and renegotiation enabled (which is the default configuration). OpenSSL TLS clients are not impacted by this issue. All OpenSSL 1.1.1 versions are affected by this issue. Users of these versions should upgrade to OpenSSL 1.1.1k. OpenSSL 1.0.2 is not impacted by this issue. Fixed in OpenSSL 1.1.1k (Affected 1.1.1-1.1.1j).
- Matched to
- Scalance Xc-200 on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 12 published vulnerabilities listed under the name Scalance Xc-200, across 0 versions.
None of Scalance Xc-200's vulnerabilities is on the list of flaws known to be exploited today.
Siemens also lists Scalance Xc-200 under more specific names, such as Scalance Xc-200 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 Scalance Xc-200. 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.