NetSight

Security Dashboard

A live picture of new vulnerabilities, flaws exploited in the wild and malicious packages.

Reset
49 matching advisories · page 2 of 2Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.8 CVE-2022-25972 An out-of-bounds write vulnerability exists in the gif2h5 functionality of HDF5 Group libhdf5 1.10.4. hdfgroup · hdf5 2022-08-22 high7.8 CVE-2022-25942 An out-of-bounds read vulnerability exists in the gif2h5 functionality of HDF5 Group libhdf5 1.10.4. hdfgroup · hdf5 2022-08-22 high8.8 CVE-2021-46242 HDF5 v1.13.1-1 was discovered to contain a heap-use-after free via the component H5AC_unpin_entry. hdfgroup · hdf5 2022-01-21 high8.8 CVE-2019-9152 An issue was discovered in the HDF HDF5 1.10.4 library. hdfgroup · hdf5 2019-02-25 high8.8 CVE-2019-9151 An issue was discovered in the HDF HDF5 1.10.4 library. hdfgroup · hdf5 2019-02-25 high8.8 CVE-2018-16438 An issue was discovered in the HDF HDF5 1.8.20 library. hdfgroup · hdf5 2018-09-04 high8.8 CVE-2018-14460 An issue was discovered in the HDF HDF5 1.8.20 library. hdfgroup · hdf5 2018-07-20 high8.8 CVE-2018-14035 An issue was discovered in the HDF HDF5 1.8.20 library. hdfgroup · hdf5 2018-07-13 high8.8 CVE-2018-14034 An issue was discovered in the HDF HDF5 1.8.20 library. hdfgroup · hdf5 2018-07-13 high8.8 CVE-2018-14033 An issue was discovered in the HDF HDF5 1.8.20 library. hdfgroup · hdf5 2018-07-13 high8.8 CVE-2018-14031 An issue was discovered in the HDF HDF5 1.8.20 library. hdfgroup · hdf5 2018-07-13 high7.8 CVE-2018-13875 An issue was discovered in the HDF HDF5 1.8.20 library. hdfgroup · hdf5 2018-07-10 high8.1 CVE-2018-11206 An out of bounds read was discovered in H5O_fill_new_decode and H5O_fill_old_decode in H5Ofill.c in the HDF HDF5 1.10.2 library. hdfgroup · hdf5 2018-05-16 high8.1 CVE-2018-11205 A out of bounds read was discovered in H5VM_memcpyvv in H5VM.c in the HDF HDF5 1.10.2 library. hdfgroup · hdf5 2018-05-16 high8.8 CVE-2017-17509 In HDF5 1.10.1, there is an out of bounds write vulnerability in the function H5G__ent_decode_vec in H5Gcache.c in libhdf5.a. hdfgroup · hdf5 2017-12-11 high8.6 CVE-2016-4333 The HDF5 1.8.16 library allocating space for the array using a value from the file has an impact within the loop for initializing said array allowing a value w… hdfgroup · hdf5 2016-11-18 high8.6 CVE-2016-4332 The library's failure to check if certain message types support a particular flag, the HDF5 1.8.16 library will cast the structure to an alternative structure … hdfgroup · hdf5 2016-11-18 high8.6 CVE-2016-4331 When decoding data out of a dataset encoded with the H5Z_NBIT decoding, the HDF5 1.8.16 library will fail to ensure that the precision is within the bounds of … hdfgroup · hdf5 2016-11-18 high8.6 CVE-2016-4330 In the HDF5 1.8.16 library's failure to check if the number of dimensions for an array read from the file is within the bounds of the space allocated for it, a… hdfgroup · hdf5 2016-11-18

Get notifications

Subscribe to new vulnerabilities and early warnings from the last seven days. Pick what matters to your stack and copy the address into any feed reader. More filters appear when you pick a type.

Format:
Open feed

Early warnings are advisories that are published before or without a CVE number, for example malicious packages, advisories with a CVE still pending and reports that are not reviewed yet. Confidence says how well an entry is checked: high, medium or low.

About this dashboard

The dashboard keeps its own index of security advisories and refreshes it every 30 minutes. It merges the national vulnerability database, package advisories, malware reports and the catalog of vulnerabilities that are exploited in the wild into one record per issue. Reports about the same flaw are combined, so nothing is listed twice.

Open any entry for the full record: description, severity vector, affected packages and versions, fixed versions, weakness class, exploitation probability and references.

Sources: the GitHub Advisory Database (reviewed advisories, malware reports and unreviewed reports), the National Vulnerability Database, the CVE Program (cve.org) for brand-new records, the OpenSSF malicious packages list, the CISA catalog of Known Exploited Vulnerabilities and Microsoft's blocklist of malicious VS Code extensions. Every entry names its sources on its detail page.

This product uses the NVD API but is not endorsed or certified by the NVD.

Reading the figures

  • Threat level: a rating computed from three numbers shown next to it: critical advisories in the last 24 hours, vulnerabilities newly confirmed as exploited this week and malware reports this week. It is a quick orientation, not an official warning level.
  • Severity: scores from 9.0 are critical, 7.0 to 8.9 high, 4.0 to 6.9 medium and 0.1 to 3.9 low. Severity describes how bad a flaw is in general. It does not know whether the component is reachable in your environment.
  • Known exploited: exploitation has been observed in real attacks. These are the entries to patch first. Entries with a fix deadline show how many days are left.
  • Early warnings: advisories that appear before or without a CVE number, for example malicious packages, reviewed advisories with a CVE still pending and reports that are not reviewed yet.
  • Priority queue: critical and high advisories of the last 7 days and everything newly exploited, ordered by exploitation status, severity and score.

Questions

Where does the data come from?
From public vulnerability databases, package advisories and the catalog of exploited vulnerabilities. NetSight collects them into its own index every 30 minutes and merges duplicates.
How do I check whether I am affected?
Search for your product or package name, open the record and compare your installed version with the affected and fixed versions. A product name alone does not mean your version is affected.
What does known exploited mean?
Exploitation of this vulnerability has been observed in real attacks. Such entries carry a date they were confirmed and, where one exists, a deadline for applying the fix.
What is an early warning?
An advisory that is published before or without a CVE number, such as a malicious package or a reviewed advisory whose CVE is still pending. They give you a head start, but the details can change.
Is a high severity always more urgent than a low one?
No. Severity measures technical impact in general. Exposure of the affected system, observed exploitation and the exploitation probability matter as much.
Can I follow new advisories automatically?
Yes. Use the notification builder further down to create an RSS, Atom or JSON feed filtered by severity, technology, ecosystem or exploitation status.