NetSight

Security Dashboard

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

Reset
50 matching advisories · page 1 of 2Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.3 CVE-2025-25944 Buffer Overflow vulnerability in Bento4 v.1.6.0-641 allows a local attacker to execute arbitrary code via the Ap4RtpAtom.cpp, specifically in AP4_RtpAtom::AP4_… axiosys · bento4 2025-02-19 high7.8 CVE-2025-25943 Buffer Overflow vulnerability in Bento4 v.1.6.0-641 allows a local attacker to execute arbitrary code via the AP4_Stz2Atom::AP4_Stz2Atom component located in A… axiosys · bento4 2025-02-19 high7.5 CVE-2024-30809 An issue was discovered in Bento4 v1.6.0-641-2-g1529b83. axiosys · bento4 2024-04-02 high7.5 CVE-2024-30807 An issue was discovered in Bento4 v1.6.0-641-2-g1529b83. axiosys · bento4 2024-04-02 high8.1 CVE-2024-31005 An issue in Bento4 Bento v.1.6.0-641 allows a remote attacker to execute arbitrary code via the Ap4MdhdAtom.cpp,AP4_MdhdAtom::AP4_MdhdAtom,mp4fragment axiosys · bento4 2024-04-02 high8.8 CVE-2024-31003 Buffer Overflow vulnerability in Bento4 Bento v.1.6.0-641 allows a remote attacker to execute arbitrary code via the AP4_MemoryByteStream::WritePartial at Ap4B… axiosys · bento4 2024-04-02 high7.3 CVE-2022-3670 A vulnerability was found in Axiomatic Bento4. axiosys · bento4 2022-10-26 high7.3 CVE-2022-3667 A vulnerability, which was classified as critical, was found in Axiomatic Bento4. axiosys · bento4 2022-10-26 high7.3 CVE-2022-3666 A vulnerability, which was classified as critical, has been found in Axiomatic Bento4. axiosys · bento4 2022-10-26 high7.3 CVE-2022-3665 A vulnerability classified as critical was found in Axiomatic Bento4. axiosys · bento4 2022-10-26 high7.3 CVE-2022-3664 A vulnerability classified as critical has been found in Axiomatic Bento4. axiosys · bento4 2022-10-26 high7.3 CVE-2022-3662 A vulnerability was found in Axiomatic Bento4. axiosys · bento4 2022-10-26 high8.8 CVE-2022-41430 Bento4 v1.6.0-639 was discovered to contain a heap overflow via the AP4_BitReader::ReadBit function in mp4mux. axiosys · bento4 2022-10-03 high8.8 CVE-2022-41429 Bento4 v1.6.0-639 was discovered to contain a heap overflow via the AP4_Atom::TypeFromString function in mp4tag. axiosys · bento4 2022-10-03 high8.8 CVE-2022-41428 Bento4 v1.6.0-639 was discovered to contain a heap overflow via the AP4_BitReader::ReadBits function in mp4mux. axiosys · bento4 2022-10-03 high7.5 CVE-2021-40941 In Bento4 1.6.0-638, there is an allocator is out of memory in the function AP4_Array<AP4_TrunAtom::Entry>::EnsureCapacity in Ap4Array.h:172, as demonstrated b… axiosys · bento4 2022-06-27 high8.1 CVE-2022-27607 Bento4 1.6.0-639 has a heap-based buffer over-read in the AP4_HvccAtom class, a different issue than CVE-2018-14531. axiosys · bento4 2022-03-21 high8.8 CVE-2021-32265 An issue was discovered in Bento4 through v1.6.0-637. axiosys · bento4 2021-09-20 high7.5 CVE-2018-10790 The AP4_CttsAtom class in Core/Ap4CttsAtom.cpp in Bento4 1.5.1.0 allows remote attackers to cause a denial of service (application crash), related to a memory … axiosys · bento4 2021-08-25 high7.5 CVE-2020-23334 A WRITE memory access in the AP4_NullTerminatedStringAtom::AP4_NullTerminatedStringAtom component of Bento4 version 06c39d9 can lead to a segmentation fault. axiosys · bento4 2021-08-17 high7.5 CVE-2020-23333 A heap-based buffer overflow exists in the AP4_CttsAtom::AP4_CttsAtom component located in /Core/Ap4Utils.h of Bento4 version 06c39d9. axiosys · bento4 2021-08-17 high7.5 CVE-2020-23332 A heap-based buffer overflow exists in the AP4_StdcFileByteStream::ReadPartial component located in /StdC/Ap4StdCFileByteStream.cpp of Bento4 version 06c39d9. axiosys · bento4 2021-08-17 high7.5 CVE-2020-23331 An issue was discovered in Bento4 version 06c39d9. axiosys · bento4 2021-08-17 high7.5 CVE-2020-23330 An issue was discovered in Bento4 version 06c39d9. axiosys · bento4 2021-08-17 high7.8 CVE-2019-20090 An issue was discovered in Bento4 1.5.1.0. axiosys · bento4 2019-12-30 high7.8 CVE-2019-17530 An issue was discovered in Bento4 1.5.1.0. axiosys · bento4 2019-10-12 high7.8 CVE-2019-17529 An issue was discovered in Bento4 1.5.1.0. axiosys · bento4 2019-10-12 high7.5 CVE-2019-17528 An issue was discovered in Bento4 1.5.1.0. axiosys · bento4 2019-10-12 high8.8 CVE-2019-15050 An issue was discovered in Bento4 1.5.1.0. axiosys · bento4 2019-08-14 high8.8 CVE-2019-15049 An issue was discovered in Bento4 1.5.1.0. axiosys · bento4 2019-08-14

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.