NetSight

Security Dashboard

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

Reset
604 matching advisories · page 20 of 21Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.5 CVE-2020-6631 An issue was discovered in GPAC version 0.8.0. gpac · gpac 2020-01-09 medium5.5 CVE-2020-6630 An issue was discovered in GPAC version 0.8.0. gpac · gpac 2020-01-09 medium5.5 CVE-2019-20208 dimC_Read in isomedia/box_code_3gpp.c in GPAC from 0.5.2 to 0.8.0 has a stack-based buffer overflow. gpac · gpac, debian · debian_linux 2020-01-02 medium5.5 CVE-2019-20171 An issue was discovered in GPAC version 0.5.2 and 0.9.0-development-20191109. gpac · gpac, debian · debian_linux 2019-12-31 medium5.5 CVE-2019-20170 An issue was discovered in GPAC version 0.8.0 and 0.9.0-development-20191109. gpac · gpac, debian · debian_linux 2019-12-31 medium5.5 CVE-2019-20169 An issue was discovered in GPAC version 0.8.0 and 0.9.0-development-20191109. gpac · gpac 2019-12-31 medium5.5 CVE-2019-20168 An issue was discovered in GPAC version 0.8.0 and 0.9.0-development-20191109. gpac · gpac 2019-12-31 medium5.5 CVE-2019-20167 An issue was discovered in GPAC version 0.8.0 and 0.9.0-development-20191109. gpac · gpac 2019-12-31 medium5.5 CVE-2019-20166 An issue was discovered in GPAC version 0.8.0 and 0.9.0-development-20191109. gpac · gpac 2019-12-31 medium5.5 CVE-2019-20165 An issue was discovered in GPAC version 0.8.0 and 0.9.0-development-20191109. gpac · gpac, debian · debian_linux 2019-12-31 medium5.5 CVE-2019-20164 An issue was discovered in GPAC version 0.8.0 and 0.9.0-development-20191109. gpac · gpac 2019-12-31 medium5.5 CVE-2019-20163 An issue was discovered in GPAC version 0.8.0 and 0.9.0-development-20191109. gpac · gpac, debian · debian_linux 2019-12-31 medium5.5 CVE-2019-20162 An issue was discovered in GPAC version 0.8.0 and 0.9.0-development-20191109. gpac · gpac, debian · debian_linux 2019-12-31 medium5.5 CVE-2019-20161 An issue was discovered in GPAC version 0.8.0 and 0.9.0-development-20191109. gpac · gpac, debian · debian_linux 2019-12-31 medium5.5 CVE-2019-20160 An issue was discovered in GPAC version 0.8.0 and 0.9.0-development-20191109. gpac · gpac 2019-12-31 medium5.5 CVE-2019-20159 An issue was discovered in GPAC version 0.8.0 and 0.9.0-development-20191109. gpac · gpac 2019-12-31 medium6.5 CVE-2018-21017 GPAC 0.7.1 has a memory leak in dinf_Read in isomedia/box_code_base.c. gpac · gpac 2019-09-16 medium6.5 CVE-2018-21016 audio_sample_entry_AddBox() at isomedia/box_code_base.c in GPAC 0.7.1 allows remote attackers to cause a denial of service (heap-based buffer over-read and app… gpac · gpac, debian · debian_linux 2019-09-16 medium6.5 CVE-2018-21015 AVC_DuplicateConfig() at isomedia/avc_ext.c in GPAC 0.7.1 allows remote attackers to cause a denial of service (NULL pointer dereference and application crash)… gpac · gpac, debian · debian_linux 2019-09-16 high7.5 CVE-2019-13618 In GPAC before 0.8.0, isomedia/isom_read.c in libgpac.a has a heap-based buffer over-read, as demonstrated by a crash in gf_m2ts_sync in media_tools/mpegts.c. gpac · gpac 2019-07-16 high7.8 CVE-2019-12483 An issue was discovered in GPAC 0.7.1. debian · debian_linux, gpac · gpac 2019-05-30 high7.5 CVE-2019-12482 An issue was discovered in GPAC 0.7.1. debian · debian_linux, gpac · gpac 2019-05-30 medium5.5 CVE-2019-12481 An issue was discovered in GPAC 0.7.1. gpac · gpac, debian · debian_linux 2019-05-30 high7.8 CVE-2019-11222 gf_bin128_parse in utils/os_divers.c in GPAC 0.7.1 has a buffer overflow issue for the crypt feature when encountering a crafted_drm_file.xml file. gpac · gpac, debian · debian_linux 2019-04-15 high7.8 CVE-2019-11221 GPAC 0.7.1 has a buffer overflow issue in gf_import_message() in media_import.c. gpac · gpac, debian · debian_linux 2019-04-15 high7.8 CVE-2018-20763 In GPAC 0.7.1 and earlier, gf_text_get_utf8_line in media_tools/text_import.c in libgpac_static.a allows an out-of-bounds write because of missing szLineConv b… gpac_project · gpac, debian · debian_linux, canonical · ubuntu_linux 2019-02-06 high7.8 CVE-2018-20762 GPAC version 0.7.1 and earlier has a buffer overflow vulnerability in the cat_multiple_files function in applications/mp4box/fileimport.c when MP4Box is used f… gpac_project · gpac, debian · debian_linux, canonical · ubuntu_linux 2019-02-06 high7.8 CVE-2018-20761 GPAC version 0.7.1 and earlier has a Buffer Overflow vulnerability in the gf_sm_load_init function in scene_manager.c in libgpac_static.a. gpac_project · gpac, debian · debian_linux, canonical · ubuntu_linux 2019-02-06 high7.8 CVE-2018-20760 In GPAC 0.7.1 and earlier, gf_text_get_utf8_line in media_tools/text_import.c in libgpac_static.a allows an out-of-bounds write because a certain -1 return val… gpac · gpac, debian · debian_linux, canonical · ubuntu_linux 2019-02-06 critical9.8 CVE-2018-13006 An issue was discovered in MP4Box in GPAC 0.7.1. debian · debian_linux, gpac · gpac, canonical · ubuntu_linux 2018-06-29

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.