NetSight

Security Dashboard

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

Reset
156 matching advisories · page 3 of 6Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
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 medium6.5 CVE-2022-41427 Bento4 v1.6.0-639 was discovered to contain a memory leak in the AP4_AvcFrameParser::Feed function in mp4mux. axiosys · bento4 2022-10-03 medium6.5 CVE-2022-41426 Bento4 v1.6.0-639 was discovered to contain a memory leak via the AP4_AtomFactory::CreateAtomFromStream function in mp4split. axiosys · bento4 2022-10-03 medium6.5 CVE-2022-41425 Bento4 v1.6.0-639 was discovered to contain a segmentation violation via the AP4_Processor::ProcessFragments function in mp4decrypt. axiosys · bento4 2022-10-03 medium6.5 CVE-2022-41424 Bento4 v1.6.0-639 was discovered to contain a memory leak via the AP4_SttsAtom::Create function in mp42hls. axiosys · bento4 2022-10-03 medium6.5 CVE-2022-41423 Bento4 v1.6.0-639 was discovered to contain a segmentation violation in the mp4fragment component. axiosys · bento4 2022-10-03 medium6.5 CVE-2022-41419 Bento4 v1.6.0-639 was discovered to contain a memory leak via the AP4_Processor::Process function in the mp4encrypt binary. axiosys · bento4 2022-10-03 medium5.5 CVE-2022-41847 An issue was discovered in Bento4 1.6.0-639. axiosys · bento4 2022-09-30 medium5.5 CVE-2022-41846 An issue was discovered in Bento4 1.6.0-639. axiosys · bento4 2022-09-30 medium5.5 CVE-2022-41845 An issue was discovered in Bento4 1.6.0-639. axiosys · bento4 2022-09-30 medium5.5 CVE-2022-41841 An issue was discovered in Bento4 through 1.6.0-639. axiosys · bento4 2022-09-30 medium5.5 CVE-2022-40775 An issue was discovered in Bento4 through 1.6.0-639. axiosys · bento4 2022-09-18 medium5.5 CVE-2022-40774 An issue was discovered in Bento4 through 1.6.0-639. axiosys · bento4 2022-09-18 medium6.5 CVE-2022-40738 An issue was discovered in Bento4 through 1.6.0-639. axiosys · bento4 2022-09-15 medium6.5 CVE-2022-40737 An issue was discovered in Bento4 through 1.6.0-639. axiosys · bento4 2022-09-15 medium6.5 CVE-2022-40736 An issue was discovered in Bento4 1.6.0-639. axiosys · bento4 2022-09-15 medium6.5 CVE-2022-40439 An memory leak issue was discovered in AP4_StdcFileByteStream::Create in mp42ts in Bento4 v1.6.0-639, allows attackers to cause a denial of service via a craft… axiosys · bento4 2022-09-14 medium6.5 CVE-2022-40438 Buffer overflow vulnerability in function AP4_MemoryByteStream::WritePartial in mp42aac in Bento4 v1.6.0-639, allows attackers to cause a denial of service via… axiosys · bento4 2022-09-14 medium5.5 CVE-2022-35165 An issue in AP4_SgpdAtom::AP4_SgpdAtom() of Bento4-1.6.0-639 allows attackers to cause a Denial of Service (DoS) via a crafted mp4 input. axiosys · bento4 2022-08-18 medium5.5 CVE-2021-40943 In Bento4 1.6.0-638, there is a null pointer reference in the function AP4_DescriptorListInspector::Action function in Ap4Descriptor.h:124 , as demonstrated by… axiosys · bento4 2022-06-28 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 medium5.5 CVE-2022-31287 An issue was discovered in Bento4 v1.2. axiosys · bento4 2022-06-10 medium5.5 CVE-2022-31285 An issue was discovered in Bento4 1.2. axiosys · bento4 2022-06-10 medium5.5 CVE-2022-31282 Bento4 MP4Dump v1.2 was discovered to contain a segmentation violation via an unknown address at /Source/C++/Core/Ap4DataBuffer.cpp:175. axiosys · bento4 2022-06-10 medium5.5 CVE-2022-29017 Bento4 v1.6.0.0 was discovered to contain a segmentation fault via the component /x86_64/multiarch/strlen-avx2.S. axiosys · bento4 2022-05-16 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

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.