NetSight

Security Dashboard

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

Reset
726 matching advisories · page 10 of 25Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.5 CVE-2024-31578 FFmpeg version n6.1.1 was discovered to contain a heap use-after-free via the av_hwframe_ctx_init function. ffmpeg · ffmpeg, fedoraproject · fedora 2024-04-17 high8.0 CVE-2023-49528 Buffer Overflow vulnerability in FFmpeg version n6.1-3-g466799d4f5, allows a local attacker to execute arbitrary code and cause a denial of service (DoS) via t… ffmpeg · ffmpeg, fedoraproject · fedora 2024-04-12 high7.5 CVE-2024-22861 Integer overflow vulnerability in FFmpeg before n6.1, allows attackers to cause a denial of service (DoS) via the avcodec/osq module. ffmpeg · ffmpeg 2024-01-27 critical9.8 CVE-2024-22862 Integer overflow vulnerability in FFmpeg before n6.1, allows remote attackers to execute arbitrary code via the JJPEG XL Parser. ffmpeg · ffmpeg 2024-01-27 critical9.8 CVE-2024-22860 Integer overflow vulnerability in FFmpeg before n6.1, allows remote attackers to execute arbitrary code via the jpegxl_anim_read_packet component in the JPEG X… ffmpeg · ffmpeg 2024-01-27 critical GHSA-j799-h2mv-f4c4 Malware in @shenmue_dsc/fluent-ffmpeg-multistream-tsMalware npm · @shenmue_dsc/fluent-ffmpeg-multistream-ts 2024-01-21 high8.8 CVE-2023-48909 An issue was discovered in Jave2 version 3.3.1, allows attackers to execute arbitrary code via the FFmpeg function. aarboard · jave2 2024-01-12 high7.8 CVE-2023-47470 Buffer Overflow vulnerability in Ffmpeg before github commit 4565747056a11356210ed8edcecb920105e40b60 allows a remote attacker to achieve an out-of-array write… ffmpeg · ffmpeg 2023-11-16 medium5.5 CVE-2023-46407 FFmpeg prior to commit bf814 was discovered to contain an out of bounds read via the dist->alphabet_size variable in the read_vlc_prefix() function. ffmpeg · ffmpeg 2023-10-27 medium5.5 CVE-2021-28429 Integer overflow vulnerability in av_timecode_make_string in libavutil/timecode.c in FFmpeg version 4.3.2, allows local attackers to cause a denial of service … ffmpeg · ffmpeg 2023-08-11 high7.5 CVE-2020-36138 An issue was discovered in decode_frame in libavcodec/tiff.c in FFmpeg version 4.3, allows remote attackers to cause a denial of service (DoS). ffmpeg · ffmpeg 2023-08-11 high8.8 CVE-2022-4907 Uninitialized Use in FFmpeg in Google Chrome prior to 108.0.5359.71 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML pag… google · chrome, fedoraproject · fedora, debian · debian_linux 2023-07-29 critical9.8 CVE-2023-39018 FFmpeg 0.7.0 and below was discovered to contain a code injection vulnerability in the component net.bramp.ffmpeg.FFmpeg.<constructor>. maven · net.bramp.ffmpeg:ffmpeg 2023-07-28 high8.1 CVE-2022-48434 libavcodec/pthread_frame.c in FFmpeg before 5.1.2, as used in VLC and other products, leaves stale hwaccel state in worker threads, which allows attackers to t… ffmpeg · ffmpeg 2023-03-29 medium5.3 CVE-2022-3341 A null pointer dereference issue was discovered in 'FFmpeg' in decode_main_header() function of libavformat/nutdec.c file. debian · debian_linux, ffmpeg · ffmpeg 2023-01-12 high7.5 CVE-2022-3109 An issue was discovered in the FFmpeg package, where vp3_decode_frame in libavcodec/vp3.c lacks check of the return value of av_malloc() and will cause a null … debian · debian_linux, fedoraproject · fedora, ffmpeg · ffmpeg 2022-12-16 medium4.3 CVE-2022-3965 A vulnerability classified as problematic was found in ffmpeg. ffmpeg · ffmpeg 2022-11-13 medium4.3 CVE-2022-3964 A vulnerability classified as problematic has been found in ffmpeg. ffmpeg · ffmpeg 2022-11-13 critical9.0 CVE-2022-2566 A heap out-of-bounds memory write exists in FFMPEG since version 5.1. ffmpeg · ffmpeg 2022-09-23 critical GHSA-fv6p-2f2f-rwpv Malware in fluetffmpegMalware npm · fluetffmpeg 2022-08-19 critical9.4 CVE-2020-28435 This affects all versions of package ffmpeg-sdk. npm · ffmpeg-sdk 2022-07-25 medium5.3 CVE-2014-125025 A vulnerability classified as problematic has been found in FFmpeg 2.0. ffmpeg · ffmpeg 2022-06-19 high7.3 CVE-2014-125024 A vulnerability was found in FFmpeg 2.0. ffmpeg · ffmpeg 2022-06-19 medium5.3 CVE-2014-125023 A vulnerability was found in FFmpeg 2.0. ffmpeg · ffmpeg 2022-06-19 medium5.3 CVE-2014-125022 A vulnerability was found in FFmpeg 2.0. ffmpeg · ffmpeg 2022-06-19 medium5.3 CVE-2014-125021 A vulnerability was found in FFmpeg 2.0 and classified as problematic. ffmpeg · ffmpeg 2022-06-19 high7.3 CVE-2014-125020 A vulnerability has been found in FFmpeg 2.0 and classified as critical. ffmpeg · ffmpeg 2022-06-19 medium5.3 CVE-2014-125019 A vulnerability, which was classified as problematic, was found in FFmpeg 2.0. ffmpeg · ffmpeg 2022-06-19 medium5.3 CVE-2014-125018 A vulnerability, which was classified as problematic, has been found in FFmpeg 2.0. ffmpeg · ffmpeg 2022-06-19 high7.3 CVE-2014-125017 A vulnerability classified as critical was found in FFmpeg 2.0. ffmpeg · ffmpeg 2022-06-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.