NetSight

Security Dashboard

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

Reset
194 matching advisories · page 4 of 7Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.8 CVE-2014-4610 Integer overflow in the get_len function in libavutil/lzo.c in FFmpeg before 0.10.14, 1.1.x before 1.1.12, 1.2.x before 1.2.7, 2.0.x before 2.0.5, 2.1.x before… ffmpeg · ffmpeg 2020-01-14 high8.8 CVE-2014-4609 Integer overflow in the get_len function in libavutil/lzo.c in Libav before 0.8.13, 9.x before 9.14, and 10.x before 10.2 allows remote attackers to execute ar… libav · libav 2020-01-14 high8.8 CVE-2019-9719 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 high8.8 CVE-2019-15942 FFmpeg through 4.2 has a "Conditional jump or move depends on uninitialised value" issue in h2645_parse because alloc_rbsp_buffer in libavcodec/h2645_parse.c m… ffmpeg · ffmpeg 2019-09-05 high8.8 CVE-2019-13312 block_cmp() in libavcodec/zmbvenc.c in FFmpeg 4.1.3 has a heap-based buffer over-read. ffmpeg · ffmpeg 2019-07-05 high8.8 CVE-2019-11339 The studio profile decoder in libavcodec/mpeg4videodec.c in FFmpeg 4.0 before 4.0.4 and 4.1 before 4.1.2 allows remote attackers to cause a denial of service (… ffmpeg · ffmpeg 2019-04-19 high8.8 CVE-2019-11338 libavcodec/hevcdec.c in FFmpeg 3.4 and 4.1.2 mishandles detection of duplicate first slices, which allows remote attackers to cause a denial of service (NULL p… ffmpeg · ffmpeg, debian · debian_linux, novell · suse_package_hub_for_suse_linux_enterprise +1 2019-04-19 high7.5 CVE-2018-15822 The flv_write_packet function in libavformat/flvenc.c in FFmpeg through 2.8 does not check for an empty audio packet, leading to an assertion failure. ffmpeg · ffmpeg, debian · debian_linux, canonical · ubuntu_linux 2018-08-23 high8.1 CVE-2018-13305 In FFmpeg 4.0.1, due to a missing check for negative values of the mquant variable, the vc1_put_blocks_clamped function in libavcodec/vc1_block.c may trigger a… ffmpeg · ffmpeg 2018-07-05 high8.1 CVE-2018-13300 In FFmpeg 3.2 and 4.0.1, an improper argument (AVCodecParameters) passed to the avpriv_request_sample function in the handle_eac3 function in libavformat/moven… ffmpeg · ffmpeg, debian · debian_linux 2018-07-05 high8.8 CVE-2018-12447 The restore_tqb_pixels function in hevc_filter.c in libavcodec, as used in libbpg 0.9.8 and other products, has an integer overflow that leads to a heap-based … libbpg_project · libbpg 2018-06-15 high7.5 CVE-2018-11102 An issue was discovered in Libav 12.3. libav · libav 2018-05-15 high8.8 CVE-2018-9841 The export function in libavfilter/vf_signature.c in FFmpeg through 3.4.2 allows remote attackers to cause a denial of service (out-of-array access) or possibl… ffmpeg · ffmpeg 2018-04-07 high7.5 CVE-2017-13299 A other vulnerability in the Android media framework (libavc). google · android 2018-04-04 high8.8 CVE-2017-13228 In function ih264d_ref_idx_reordering of libavc, there is an out-of-bounds write due to modCount being defined as an unsigned character. google · android 2018-02-12 high8.8 CVE-2012-5360 Libavcodec in FFmpeg before 0.11 allows remote attackers to execute arbitrary code via a crafted QT file. ffmpeg · ffmpeg 2018-02-08 high8.8 CVE-2012-5359 Libavcodec in FFmpeg before 0.11 allows remote attackers to execute arbitrary code via a crafted ASF file. ffmpeg · ffmpeg 2018-02-08 high8.8 CVE-2018-5766 In Libav through 12.2, there is an invalid memcpy in the av_packet_ref function of libavcodec/avpacket.c. libav · libav 2018-01-18 high8.8 CVE-2018-5684 In Libav through 12.2, there is an invalid memcpy call in the ff_mov_read_stsd_entries function of libavformat/mov.c. libav · libav 2018-01-14 high7.5 CVE-2017-13189 A vulnerability in the Android media framework (libavc) related to handling dec_hdl memory allocation failures. google · android 2018-01-12 high7.5 CVE-2017-13186 A vulnerability in the Android media framework (libavc) related to incorrect use of mmco parameters. google · android 2018-01-12 high8.8 CVE-2017-0877 A remote code execution vulnerability in the Android media framework (libavc). google · android 2017-12-06 high8.8 CVE-2017-0876 A remote code execution vulnerability in the Android media framework (libavc). google · android 2017-12-06 high8.8 CVE-2017-17130 The ff_free_picture_tables function in libavcodec/mpegpicture.c in Libav 12.2 allows remote attackers to cause a denial of service (heap-based buffer overflow … libav · libav 2017-12-04 high8.8 CVE-2017-17129 The ff_vc1_mc_4mv_chroma4 function in libavcodec/vc1_mc.c in Libav 12.2 allows remote attackers to cause a denial of service (segmentation fault and applicatio… libav · libav 2017-12-04 high7.8 CVE-2017-0833 A remote code execution vulnerability in the Android media framework (libavc). google · android 2017-11-16 high8.8 CVE-2017-14034 The restore_tqb_pixels function in hevc_filter.c in libavcodec, as used in libbpg 0.9.7 and other products, miscalculates a memcpy destination address, which a… libbpg_project · libbpg 2017-11-16 high7.5 CVE-2017-16803 In Libav through 11.11 and 12.x through 12.1, the smacker_decode_tree function in libavcodec/smacker.c does not properly restrict tree recursion, which allows … libav · libav 2017-11-13 high8.8 CVE-2017-15672 The read_header function in libavcodec/ffv1dec.c in FFmpeg 2.4 and 3.3.4 and possibly earlier allows remote attackers to have unspecified impact via a crafted … ffmpeg · ffmpeg, debian · debian_linux 2017-11-06 high8.8 CVE-2017-14767 The sdp_parse_fmtp_config_h264 function in libavformat/rtpdec_h264.c in FFmpeg before 3.3.4 mishandles empty sprop-parameter-sets values, which allows remote a… ffmpeg · ffmpeg 2017-09-27

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.