NetSight

Security Dashboard

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

Reset
317 matching advisories · page 5 of 11Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.5 CVE-2020-20445 FFmpeg 4.2 is affected by a Divide By Zero issue via libavcodec/lpc.h, which allows a remote malicious user to cause a Denial of Service. ffmpeg · ffmpeg, debian · debian_linux 2021-05-25 medium6.5 CVE-2020-35964 track_header in libavformat/vividas.c in FFmpeg 4.3.1 has an out-of-bounds write because of incorrect extradata packing. ffmpeg · ffmpeg 2021-01-03 medium5.5 CVE-2020-0323 In libavb, there is a possible out of bounds read due to a missing bounds check. google · android 2020-09-17 medium5.5 CVE-2020-13904 FFmpeg 2.8 and 4.2.3 has a use-after-free via a crafted EXTINF duration in an m3u8 file because parse_playlist in libavformat/hls.c frees a pointer, and later … ffmpeg · ffmpeg, canonical · ubuntu_linux, debian · debian_linux 2020-06-07 medium6.5 CVE-2019-9411 In libavc there is a possible information disclosure due to uninitialized data. google · android 2019-09-27 medium6.5 CVE-2019-9410 In libavc there is a possible information disclosure due to uninitialized data. google · android 2019-09-27 medium6.5 CVE-2019-9408 In libavc there is a possible information disclosure due to uninitialized data. google · android 2019-09-27 medium6.5 CVE-2019-9361 In libavc there is a possible information disclosure due to uninitialized data. google · android 2019-09-27 medium6.5 CVE-2019-9359 In libavc there is a possible information disclosure due to uninitialized data. google · android 2019-09-27 medium6.5 CVE-2019-9338 In libavc there is a possible information disclosure due to uninitialized data. google · android 2019-09-27 medium6.5 CVE-2019-9337 In libavc there is a possible information disclosure due to uninitialized data. google · android 2019-09-27 medium6.5 CVE-2019-9336 In libavc there is a possible information disclosure due to uninitialized data. google · android 2019-09-27 medium6.5 CVE-2019-9335 In libavc there is a possible information disclosure due to uninitialized data. google · android 2019-09-27 medium6.5 CVE-2019-9322 In libavc there is a possible information disclosure due to uninitialized data. google · android 2019-09-27 medium6.5 CVE-2019-9321 In libavc, there is a missing variable initialization. google · android 2019-09-27 medium6.5 CVE-2019-9320 In libavc, there is a missing variable initialization. google · android 2019-09-27 medium6.5 CVE-2019-9319 In libavc, there is a missing variable initialization. google · android 2019-09-27 medium6.5 CVE-2019-9314 In libavc, there is a missing variable initialization. google · android 2019-09-27 medium6.5 CVE-2019-9252 In libavc there is a possible out of bounds read due to uninitialized data. google · android 2019-09-27 medium6.5 CVE-2019-9720 A stack-based buffer overflow in the subtitle decoder in Libav 12.3 allows attackers to corrupt the stack via a crafted video file in Matroska format, because … libav · libav 2019-09-19 medium6.5 CVE-2019-9717 In Libav 12.3, a denial of service in the subtitle decoder allows attackers to hog the CPU via a crafted video file in Matroska format, because srt_to_ass in l… libav · libav 2019-09-19 medium6.5 CVE-2019-14443 An issue was discovered in Libav 12.3. libav · libav, debian · debian_linux 2019-07-30 medium6.5 CVE-2019-14442 In mpc8_read_header in libavformat/mpc8.c in Libav 12.3, an input file can result in an avio_seek infinite loop and hang, with 100% CPU consumption. libav · libav, debian · debian_linux 2019-07-30 medium6.5 CVE-2019-14441 An issue was discovered in Libav 12.3. libav · libav 2019-07-30 medium6.5 CVE-2019-14372 In Libav 12.3, there is an infinite loop in the function wv_read_block_header() in the file wvdec.c. libav · libav 2019-07-28 medium6.5 CVE-2019-14371 An issue was discovered in Libav 12.3. libav · libav 2019-07-28 medium6.5 CVE-2019-13390 In FFmpeg 4.1.3, there is a division by zero at adx_write_trailer in libavformat/rawenc.c. ffmpeg · ffmpeg 2019-07-07 medium6.5 CVE-2017-5984 In libavcodec in Libav 9.21, ff_h264_execute_ref_pic_marking() has a heap-based buffer over-read. libav · libav 2019-05-22 medium6.5 CVE-2019-1000016 FFMPEG version 4.1 contains a CWE-129: Improper Validation of Array Index vulnerability in libavcodec/cbs_av1.c that can result in Denial of service. ffmpeg · ffmpeg 2019-02-04 medium6.5 CVE-2018-20001 In Libav 12.3, there is a floating point exception in the range_decode_culshift function (called from range_decode_bits) in libavcodec/apedec.c that will lead … libav · libav 2018-12-10

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.