Santricity Cloud Connector vulnerabilitiesRanked by how likely they are to be used.

Product0 versions
The short answer

Santricity Cloud Connector is made by Netapp. We track 27 published vulnerabilities in it, across 0 versions. None of them is on the list of flaws known to be exploited today. If you run Santricity Cloud Connector, keep it on a version the vendor still supports.

See the riskiest flaws

We keep watching the known-exploited list.

Known exploited

Which Santricity Cloud Connector vulnerabilities are being exploited?

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

None of Santricity Cloud Connector's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.

Exploit likelihood

Which Santricity Cloud Connector 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. 85%

    In Apache httpd 2.4.0 to 2.4.29, the expression specified in <FilesMatch> could match '$' to a newline character in a malicious filename, rather than matching only the end of the filename.

    CVSS8.1Published26 Mar 2018
  2. 82%

    In Eclipse Jetty 9.4.37.v20210219 to 9.4.38.v20210224, the default compliance mode allows requests with URIs that contain %2e or %2e%2e segments to access protected resources within the WEB-INF directory.

    CVSS5.3Published1 Apr 2021
  3. 70%

    A specially crafted HTTP request header could have crashed the Apache HTTP Server prior to version 2.4.30 due to an out of bound read while preparing data to be cached in shared memory.

    CVSS7.5Published26 Mar 2018
  4. 54%

    In Eclipse Jetty 7.2.2 to 9.4.38, 10.0.0.alpha0 to 10.0.1, and 11.0.0.alpha0 to 11.0.1, CPU usage can reach 100% upon receiving a large invalid TLS frame.

    CVSS7.5Published1 Apr 2021
  5. 20%

    In Apache HTTP Server 2.4 release 2.4.37 and prior, mod_session checks the session expiry time before decoding the session.

    CVSS7.5Published30 Jan 2019
  6. 20%

    In Apache HTTP server versions 2.4.37 and prior, by sending request bodies in a slow loris way to plain resources, the h2 stream for that request unnecessarily occupied a server thread cleaning up that incoming data.

    CVSS5.3Published30 Jan 2019
  7. 17%

    In Apache httpd 2.0.23 to 2.0.65, 2.2.0 to 2.2.34, and 2.4.0 to 2.4.29, mod_authnz_ldap, if configured with AuthLDAPCharsetConfig, uses the Accept-Language header value to lookup the right charset encoding when...

    CVSS7.5Published26 Mar 2018
  8. 15%

    A specially crafted request could have crashed the Apache HTTP Server prior to version 2.4.30, due to an out of bound access after a size limit is reached by reading the HTTP header.

    CVSS5.9Published26 Mar 2018
  9. 15%

    In Eclipse Jetty, versions 9.2.x and older, 9.3.x (all configurations), and 9.4.x (non-default configuration with RFC2616 compliance enabled), transfer-encoding chunks are handled poorly.

    CVSS9.8Published26 Jun 2018
Precursor Intelligence

Running Santricity Cloud Connector? 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 27 published vulnerabilities listed under the name Santricity Cloud Connector, across 0 versions.

None of Santricity Cloud Connector's vulnerabilities is on the list of flaws known to be exploited today.

Create a Precursor Intelligence account and track Santricity Cloud Connector. 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.