NetSight

Security Dashboard

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

Reset
604 matching advisories · page 11 of 21Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
critical9.1 CVE-2023-2838 Out-of-bounds Read in GitHub repository gpac/gpac prior to 2.2.2. gpac · gpac 2023-05-22 medium5.5 CVE-2023-2837 Stack-based Buffer Overflow in GitHub repository gpac/gpac prior to 2.2.2. gpac · gpac 2023-05-22 medium5.0 CVE-2023-21090 In parseUsesPermission of ParsingPackageUtils.java, there is a possible boot loop due to resource exhaustion. google · android 2023-04-19 medium5.3 CVE-2023-28968 An Improperly Controlled Sequential Memory Allocation vulnerability in the Juniper Networks Deep Packet Inspection-Decoder (JDPI-Decoder) Application Signature… juniper · appid_service_sigpack, juniper · jdpi-decoder_engine, juniper · junos 2023-04-17 high7.8 CVE-2021-46879 An issue was discovered in Treasure Data Fluent Bit 1.7.1, a wrong variable is used to get the msgpack data resulting in a heap overflow in flb_msgpack_gelf_va… treasuredata · fluent_bit 2023-04-11 high7.8 CVE-2021-46878 An issue was discovered in Treasure Data Fluent Bit 1.7.1, erroneous parsing in flb_pack_msgpack_to_json_format leads to type confusion bug that interprets wha… treasuredata · fluent_bit 2023-04-11 high7.8 CVE-2023-1654 Denial of Service in GitHub repository gpac/gpac prior to 2.4.0. gpac · gpac 2023-03-27 high7.8 CVE-2023-1655 Heap-based Buffer Overflow in GitHub repository gpac/gpac prior to 2.4.0. gpac · gpac 2023-03-27 medium5.3 CVE-2023-1452 A vulnerability was found in GPAC 2.3-DEV-rev35-gbbca86917-master. gpac · gpac 2023-03-17 medium5.3 CVE-2023-1449 A vulnerability has been found in GPAC 2.3-DEV-rev35-gbbca86917-master and classified as problematic. gpac · gpac 2023-03-17 medium5.3 CVE-2023-1448 A vulnerability, which was classified as problematic, was found in GPAC 2.3-DEV-rev35-gbbca86917-master. gpac · gpac 2023-03-17 high7.8 CVE-2023-0866 Heap-based Buffer Overflow in GitHub repository gpac/gpac prior to 2.3.0-DEV. gpac · gpac 2023-02-16 medium6.3 CVE-2023-0841 A vulnerability, which was classified as critical, has been found in GPAC 2.3-DEV-rev40-g3602a5ded. gpac · gpac 2023-02-15 high7.8 CVE-2023-0819 Heap-based Buffer Overflow in GitHub repository gpac/gpac prior to v2.3.0-DEV. gpac · gpac 2023-02-13 medium5.5 CVE-2023-0818 Off-by-one Error in GitHub repository gpac/gpac prior to v2.3.0-DEV. gpac · gpac 2023-02-13 high7.8 CVE-2023-0817 Buffer Over-read in GitHub repository gpac/gpac prior to v2.3.0-DEV. gpac · gpac 2023-02-13 high7.8 CVE-2023-0770 Stack-based Buffer Overflow in GitHub repository gpac/gpac prior to 2.2. gpac · gpac, debian · debian_linux 2023-02-09 high7.8 CVE-2023-0760 Heap-based Buffer Overflow in GitHub repository gpac/gpac prior to V2.1.0-DEV. gpac · gpac 2023-02-09 high7.8 CVE-2023-23145 GPAC version 2.2-rev0-gab012bbfb-master was discovered to contain a memory leak in lsr_read_rare_full function. gpac · gpac 2023-01-20 medium5.5 CVE-2023-23144 Integer overflow vulnerability in function Q_DecCoordOnUnitSphere file bifs/unquantize.c in GPAC version 2.2-rev0-gab012bbfb-master. gpac · gpac 2023-01-20 high7.8 CVE-2023-23143 Buffer overflow vulnerability in function avc_parse_slice in file media_tools/av_parsers.c. gpac · gpac 2023-01-20 high7.8 CVE-2023-0358 Use After Free in GitHub repository gpac/gpac prior to 2.3.0-DEV. gpac · gpac 2023-01-18 high7.8 CVE-2022-47663 GPAC MP4box 2.1-DEV-rev649-ga8f438d20 is vulnerable to buffer overflow in h263dmx_process filters/reframe_h263.c:609 gpac · gpac 2023-01-05 medium5.5 CVE-2022-47662 GPAC MP4Box 2.1-DEV-rev649-ga8f438d20 has a segment fault (/stack overflow) due to infinite recursion in Media_GetSample isomedia/media.c:662 gpac · gpac 2023-01-05 high7.8 CVE-2022-47661 GPAC MP4Box 2.1-DEV-rev649-ga8f438d20 is vulnerable to Buffer Overflow via media_tools/av_parsers.c:4988 in gf_media_nalu_add_emulation_bytes gpac · gpac 2023-01-05 high7.8 CVE-2022-47660 GPAC MP4Box 2.1-DEV-rev644-g5c4df2a67 is has an integer overflow in isomedia/isom_write.c gpac · gpac 2023-01-05 high7.8 CVE-2022-47659 GPAC MP4box 2.1-DEV-rev644-g5c4df2a67 is vulnerable to Buffer Overflow in gf_bs_read_data gpac · gpac 2023-01-05 high7.8 CVE-2022-47658 GPAC MP4Box 2.1-DEV-rev644-g5c4df2a67 is vulnerable to buffer overflow in function gf_hevc_read_vps_bs_internal of media_tools/av_parsers.c:8039 gpac · gpac 2023-01-05 high7.8 CVE-2022-47657 GPAC MP4Box 2.1-DEV-rev644-g5c4df2a67 is vulnerable to buffer overflow in function hevc_parse_vps_extension of media_tools/av_parsers.c:7662 gpac · gpac 2023-01-05 high7.8 CVE-2022-47656 GPAC MP4box 2.1-DEV-rev617-g85ce76efd is vulnerable to Buffer Overflow in gf_hevc_read_sps_bs_internal function of media_tools/av_parsers.c:8273 gpac · gpac 2023-01-05

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.