Scalance Sc632-2c Firmware vulnerabilitiesRanked by how likely they are to be used.

Product2 versions
The short answer

Scalance Sc632-2c Firmware is made by Siemens. We track 11 published vulnerabilities in it, across 2 versions. None of them is on the list of flaws known to be exploited today. If you run Scalance Sc632-2c Firmware, keep it on a version the vendor still supports.

See the riskiest flaws

We keep watching the known-exploited list.

Known exploited

Which Scalance Sc632-2c Firmware vulnerabilities are being exploited?

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

None of Scalance Sc632-2c Firmware's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.

Exploit likelihood

Which Scalance Sc632-2c Firmware 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. 52%

    zlib before 1.2.12 allows memory corruption when deflating (i.e., when compressing) if the input has many distant matches.

    CVSS7.5Published25 Mar 2022
  2. 36%

    curl < 7.84.0 supports "chained" HTTP compression algorithms, meaning that a serverresponse can be compressed multiple times and potentially with different algorithms.

    CVSS6.5Published7 Jul 2022
  3. 31%

    A malicious server can serve excessive amounts of `Set-Cookie:` headers in a HTTP response to curl and curl < 7.84.0 stores all of them.

    CVSS4.3Published7 Jul 2022
  4. 5.3%

    The in-memory certificate cache in strongSwan before 5.9.4 has a remote integer overflow upon receiving many requests with different certificates to fill the cache and later trigger the replacement of cache entries.

    CVSS7.5Published18 Oct 2021
  5. 1.8%

    Affected devices do not properly sanitize an input field.

    CVSS9.1Published10 Aug 2022
  6. 1.3%

    A use-after-free in Busybox 1.35-x's awk applet leads to denial of service and possibly code execution when processing a crafted awk pattern in the copyvar function.

    CVSS7.8Published18 May 2022
  7. 1.0%

    Affected devices do not properly sanitize data introduced by an user when rendering the web interface.

    CVSS4.8Published10 Aug 2022
  8. 1.0%

    A vulnerability has been identified in RUGGEDCOM RM1224 (All versions >= V4.3 and < V6.4), SCALANCE M-800 (All versions >= V4.3 and < V6.4), SCALANCE S615 (All versions >= V4.3 and < V6.4), SCALANCE SC-600 Family...

    CVSS8.8Published15 Mar 2021
  9. 0.7%

    Affected devices do not check the TFTP blocksize correctly.

    CVSS2.7Published13 Dec 2022
  10. 0.3%

    Affected devices store the CLI user passwords encrypted in flash memory.

    CVSS5.7Published13 Dec 2022
Precursor Intelligence

Running Scalance Sc632-2c Firmware? 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 11 published vulnerabilities listed under the name Scalance Sc632-2c Firmware, across 2 versions.

None of Scalance Sc632-2c Firmware's vulnerabilities is on the list of flaws known to be exploited today.

Create a Precursor Intelligence account and track Scalance Sc632-2c Firmware. 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.