NetSight

Security Dashboard

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

Reset
604 matching advisories · page 10 of 21Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.5 CVE-2023-5595 Denial of Service in GitHub repository gpac/gpac prior to 2.3.0-DEV. gpac · gpac 2023-10-16 high7.8 CVE-2023-5586 NULL Pointer Dereference in GitHub repository gpac/gpac prior to 2.3.0-DEV. gpac · gpac 2023-10-15 medium5.5 CVE-2023-42298 An issue in GPAC GPAC v.2.2.1 and before allows a local attacker to cause a denial of service via the Q_DecCoordOnUnitSphere function of file src/bifs/unquanti… gpac · gpac 2023-10-12 high7.7 CVE-2023-5520 Out-of-bounds Read in GitHub repository gpac/gpac prior to 2.2.2. gpac · gpac 2023-10-11 high7.1 CVE-2023-5377 Out-of-bounds Read in GitHub repository gpac/gpac prior to v2.2.2-DEV. gpac · gpac 2023-10-04 medium5.9 CVE-2023-41855 Auth. regpacks · regpack 2023-10-02 medium5.5 CVE-2023-41000 GPAC through 2.2.1 has a use-after-free vulnerability in the function gf_bifs_flush_command_list in bifs/memory_decoder.c. gpac · gpac 2023-09-11 medium5.5 CVE-2023-4778 Out-of-bounds Read in GitHub repository gpac/gpac prior to 2.3-DEV. gpac · gpac 2023-09-05 medium5.5 CVE-2023-4758 Buffer Over-read in GitHub repository gpac/gpac prior to 2.3-DEV. gpac · gpac 2023-09-04 medium5.5 CVE-2023-4755 Use After Free in GitHub repository gpac/gpac prior to 2.3-DEV. gpac · gpac 2023-09-04 medium5.5 CVE-2023-4756 Stack-based Buffer Overflow in GitHub repository gpac/gpac prior to 2.3-DEV. gpac · gpac 2023-09-04 medium5.5 CVE-2023-4754 Out-of-bounds Write in GitHub repository gpac/gpac prior to 2.3-DEV. gpac · gpac 2023-09-04 medium5.5 CVE-2023-4722 Integer Overflow or Wraparound in GitHub repository gpac/gpac prior to 2.3-DEV. gpac · gpac 2023-09-01 medium5.5 CVE-2023-4721 Out-of-bounds Read in GitHub repository gpac/gpac prior to 2.3-DEV. gpac · gpac 2023-09-01 medium5.5 CVE-2023-4720 Floating Point Comparison with Incorrect Operator in GitHub repository gpac/gpac prior to 2.3-DEV. gpac · gpac 2023-09-01 medium5.5 CVE-2023-4683 NULL Pointer Dereference in GitHub repository gpac/gpac prior to 2.3-DEV. gpac · gpac 2023-08-31 medium5.5 CVE-2023-4682 Heap-based Buffer Overflow in GitHub repository gpac/gpac prior to 2.3-DEV. gpac · gpac 2023-08-31 medium5.5 CVE-2023-4681 NULL Pointer Dereference in GitHub repository gpac/gpac prior to 2.3-DEV. gpac · gpac 2023-08-31 medium5.5 CVE-2023-4678 Divide By Zero in GitHub repository gpac/gpac prior to 2.3-DEV. gpac · gpac 2023-08-31 medium5.5 CVE-2023-39562 GPAC v2.3-DEV-rev449-g5948e4f70-master was discovered to contain a heap-use-after-free via the gf_bs_align function at bitstream.c. gpac · gpac 2023-08-28 medium5.5 CVE-2023-37767 GPAC v2.3-DEV-rev381-g817a848f6-master was discovered to contain a segmentation violation in the BM_ParseIndexValueReplace function at /lib/libgpac.so. gpac · gpac 2023-07-11 medium5.5 CVE-2023-37766 GPAC v2.3-DEV-rev381-g817a848f6-master was discovered to contain a segmentation violation in the gf_isom_remove_user_data function at /lib/libgpac.so. gpac · gpac 2023-07-11 medium5.5 CVE-2023-37765 GPAC v2.3-DEV-rev381-g817a848f6-master was discovered to contain a segmentation violation in the gf_dump_vrml_sffield function at /lib/libgpac.so. gpac · gpac 2023-07-11 medium5.5 CVE-2023-37174 GPAC v2.3-DEV-rev381-g817a848f6-master was discovered to contain a segmentation violation in the dump_isom_scene function at /mp4box/filedump.c. gpac · gpac 2023-07-11 high7.1 CVE-2023-3523 Out-of-bounds Read in GitHub repository gpac/gpac prior to 2.2.2. gpac · gpac 2023-07-06 low3.3 CVE-2023-3291 Heap-based Buffer Overflow in GitHub repository gpac/gpac prior to 2.2.2. gpac · gpac 2023-06-16 high7.1 CVE-2023-3013 Unchecked Return Value in GitHub repository gpac/gpac prior to 2.2.2. gpac · gpac 2023-05-31 high7.8 CVE-2023-3012 NULL Pointer Dereference in GitHub repository gpac/gpac prior to 2.2.2. gpac · gpac 2023-05-31 critical9.8 CVE-2023-2840 NULL Pointer Dereference in GitHub repository gpac/gpac prior to 2.2.2. gpac · gpac 2023-05-22 high7.5 CVE-2023-2839 Divide By Zero in GitHub repository gpac/gpac prior to 2.2.2. gpac · gpac 2023-05-22

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.