Solidfire Baseboard Management Controller vulnerabilitiesAnd the versions its exploited flaws hit.

Product1 known exploited0 versions
The short answer

Solidfire Baseboard Management Controller is made by Netapp. We track 86 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 3 November 2021. Netapp lists newer releases under their own names, such as Solidfire Baseboard Management Controller Firmware, so check those pages too.

Check your version

The most recent Solidfire Baseboard Management Controller flaw added to the known-exploited list is CVE-2019-2215, on 3 November 2021. We keep watching the known-exploited list.

Other names

Is Solidfire Baseboard Management Controller listed under other names? Yes.

Netapp also lists Solidfire Baseboard Management Controller under more specific names, such as Solidfire Baseboard Management Controller 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.

Versions

Which versions of Solidfire Baseboard Management Controller 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 Solidfire Baseboard Management Controller 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. 7.8
    CVE-2019-2215HighKnown exploited
    Android Kernel Use-After-Free Vulnerability

    Android Kernel contains a use-after-free vulnerability in binder.c that allows for privilege escalation from an application to the Linux Kernel.

    Chance of use72%Known exploited since3 Nov 2021
Exploit likelihood

Which Solidfire Baseboard Management Controller 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. 72%
    CVE-2019-2215HighKnown exploited

    A use-after-free in binder.c allows an elevation of privilege from an application to the Linux Kernel.

    CVSS7.8Published11 Oct 2019
  2. 7.5%

    Double-free vulnerability in the FTP-kerberos code in cURL 7.52.0 to 7.65.3.

    CVSS9.8Published16 Sep 2019
  3. 6.7%

    When sending data to an MQTT server, libcurl <= 7.73.0 and 7.78.0 could in some circumstances erroneously keep a pointer to an already freed memory area and both use that again in a subsequent call to send data and...

    CVSS9.1Published23 Sep 2021
  4. 5.2%

    A memory leak in the gs_can_open() function in drivers/net/can/usb/gs_usb.c in the Linux kernel before 5.3.11 allows attackers to cause a denial of service (memory consumption) by triggering usb_submit_urb()...

    CVSS7.5Published18 Nov 2019
  5. 5.2%

    gadget_dev_desc_UDC_store in drivers/usb/gadget/configfs.c in the Linux kernel 3.16 through 5.6.13 relies on kstrdup without considering the possibility of an internal '\0' value, which allows attackers to trigger an...

    CVSS6.5Published18 May 2020
  6. 5.2%

    An out-of-bounds memory write flaw was found in how the Linux kernel’s Voice Over IP H.323 connection tracking functionality handled connections on ipv6 port 1720.

    CVSS8.1Published2 Dec 2020
  7. 4.5%

    A user can tell curl >= 7.20.0 and <= 7.78.0 to require a successful upgrade to TLS when speaking to an IMAP, POP3 or FTP server (`--ssl-reqd` on the command line or`CURLOPT_USE_SSL` set to `CURLUSESSL_CONTROL` or...

    CVSS7.5Published29 Sep 2021
  8. 4.0%

    Two memory leaks in the v3d_submit_cl_ioctl() function in drivers/gpu/drm/v3d/v3d_gem.c in the Linux kernel before 5.3.11 allow attackers to cause a denial of service (memory consumption) by triggering kcalloc() or...

    CVSS7.5Published18 Nov 2019
  9. 3.6%

    A memory leak in the adis_update_scan_mode() function in drivers/iio/imu/adis_buffer.c in the Linux kernel before 5.3.9 allows attackers to cause a denial of service (memory consumption), aka CID-ab612b1daf41.

    CVSS7.5Published18 Nov 2019
  10. 3.5%

    In the Linux kernel 5.0.21, mounting a crafted ext4 filesystem image, performing some operations, and unmounting can lead to a use-after-free in ext4_put_super in fs/ext4/super.c, related to dump_orphan_list in...

    CVSS7.8Published8 Dec 2019
Precursor Intelligence

Running Solidfire Baseboard Management Controller? 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 86 published vulnerabilities listed under the name Solidfire Baseboard Management Controller, across 0 versions. The most recent Solidfire Baseboard Management Controller flaw added to the known-exploited list is CVE-2019-2215, on 3 November 2021.

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

Netapp also lists Solidfire Baseboard Management Controller under more specific names, such as Solidfire Baseboard Management Controller 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 Solidfire Baseboard Management Controller. 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.