E-Series Santricity Web Services vulnerabilitiesAnd the versions its exploited flaws hit.

Product1 known exploited0 versions
The short answer

E-Series Santricity Web Services is made by Netapp. We track 99 published vulnerabilities listed under that exact name, across 0 versions. 1 of them is on the list of flaws known to be exploited, the newest added on 12 May 2023. Netapp lists newer releases under their own names, such as E-Series Santricity Web Services Proxy, so check those pages too.

Check your version

The most recent E-Series Santricity Web Services flaw added to the known-exploited list is CVE-2016-3427, on 12 May 2023. We keep watching the known-exploited list.

Other names

Is E-Series Santricity Web Services listed under other names? Yes.

Netapp also lists E-Series Santricity Web Services under more specific names, such as E-Series Santricity Web Services Proxy. 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.

Versions

Which versions of E-Series Santricity Web Services do the exploited flaws hit?

Each exploited flaw lists the versions it affects, as published by the vendor. Find your version, then patch.

Known exploited

Which E-Series Santricity Web Services vulnerabilities are being exploited?

1 flaw is on the government list of vulnerabilities known to be exploited. These are the ones criminals are using now, so they go first, whatever their severity score says.

  1. 9.8
    CVE-2016-3427CriticalKnown exploited
    Oracle Java SE and JRockit Unspecified Vulnerability

    Oracle Java SE and JRockit contains an unspecified vulnerability that allows remote attackers to affect confidentiality, integrity, and availability via vectors related to Java Management Extensions (JMX).

    Chance of use92%Known exploited since12 May 2023
Exploit likelihood

Which E-Series Santricity Web Services 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. >99%

    For Eclipse Jetty versions 9.4.37-9.4.42, 10.0.1-10.0.5 & 11.0.1-11.0.5, URIs can be crafted using some encoded characters to access the content of the WEB-INF directory and/or bypass some security constraints.

    CVSS5.3Published15 Jul 2021
  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. 78%

    In Eclipse Jetty 9.4.6.v20170531 to 9.4.36.v20210114 (inclusive), 10.0.0, and 11.0.0 when Jetty handles a request containing multiple Accept headers with a large number of “quality” (i.e.

    CVSS5.2Published26 Feb 2021
  4. 77%

    Vulnerability in the Oracle Java SE, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: Libraries).

    CVSS7.5Published19 Apr 2022
  5. 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
  6. 17%

    There is a flaw in the xml entity encoding functionality of libxml2 in versions before 2.9.11.

    CVSS8.6Published19 May 2021
  7. 16%

    Vulnerability in the Java SE, Java SE Embedded, JRockit component of Oracle Java SE (subcomponent: Networking).

    CVSS5.3Published19 Oct 2017
  8. 16%

    Vulnerability in the Java SE, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: Swing).

    CVSS5.3Published20 Oct 2021
Precursor Intelligence

Running E-Series Santricity Web Services? 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 99 published vulnerabilities listed under the name E-Series Santricity Web Services, across 0 versions. The most recent E-Series Santricity Web Services flaw added to the known-exploited list is CVE-2016-3427, on 12 May 2023.

1 is on the list of flaws known to be exploited. The most recently added is CVE-2016-3427.

Netapp also lists E-Series Santricity Web Services under more specific names, such as E-Series Santricity Web Services Proxy. 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 E-Series Santricity Web Services. 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.