NetSight

Security Dashboard

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

Reset
156 matching advisories · page 4 of 6Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
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 medium6.5 CVE-2020-21066 An issue was discovered in Bento4 v1.5.1.0. axiosys · bento4 2021-08-13 medium6.5 CVE-2021-35307 An issue was discovered in Bento4 through v1.6.0-636. axiosys · bento4 2021-08-05 medium6.5 CVE-2021-35306 An issue was discovered in Bento4 through v1.6.0-636. axiosys · bento4 2021-08-05 medium6.5 CVE-2020-19722 An unhandled memory allocation failure in Core/Ap4Atom.cpp of Bento 1.5.1-628 causes a direct copy to NULL pointer dereference, leading to a denial of service … axiosys · bento4 2021-07-13 medium6.5 CVE-2020-19721 A heap buffer overflow vulnerability in Ap4TrunAtom.cpp of Bento 1.5.1-628 may lead to an out-of-bounds write while running mp42aac, leading to system crashes … axiosys · bento4 2021-07-13 medium6.5 CVE-2020-19720 An unhandled memory allocation failure in Core/AP4IkmsAtom.cpp of Bento 1.5.1-628 causes a NULL pointer dereference, leading to a denial of service (DOS). axiosys · bento4 2021-07-13 medium6.5 CVE-2020-19719 A buffer overflow vulnerability in Ap4ElstAtom.cpp of Bento 1.5.1-628 leads to a denial of service (DOS). axiosys · bento4 2021-07-13 medium6.5 CVE-2020-19718 An unhandled memory allocation failure in Core/Ap4Atom.cpp of Bento 1.5.1-628 causes a NULL pointer dereference, leading to a denial of service (DOS). axiosys · bento4 2021-07-13 medium6.5 CVE-2020-19717 An unhandled memory allocation failure in Core/Ap48bdlAtom.cpp of Bento 1.5.1-628 causes a NULL pointer dereference, leading to a denial of service (DOS). axiosys · bento4 2021-07-13 medium5.5 CVE-2020-23912 An issue was discovered in Bento4 through v1.6.0-637. axiosys · bento4 2021-04-21 medium5.5 CVE-2019-20092 An issue was discovered in Bento4 1.5.1.0. axiosys · bento4 2019-12-30 medium5.5 CVE-2019-20091 An issue was discovered in Bento4 1.5.1.0. axiosys · bento4 2019-12-30 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 medium6.5 CVE-2019-17454 Bento4 1.5.1.0 has a NULL pointer dereference in AP4_Descriptor::GetTag in Core/Ap4Descriptor.h, related to AP4_StsdAtom::GetSampleDescription in Core/Ap4StsdA… axiosys · bento4 2019-10-10 medium6.5 CVE-2019-17453 Bento4 1.5.1.0 has a NULL pointer dereference in AP4_DescriptorListWriter::Action in Core/Ap4Descriptor.h, related to AP4_IodsAtom::WriteFields in Core/Ap4Iods… axiosys · bento4 2019-10-10 medium6.5 CVE-2019-17452 Bento4 1.5.1.0 has a NULL pointer dereference in AP4_DescriptorListInspector::Action in Core/Ap4Descriptor.h, related to AP4_IodsAtom::InspectFields in Core/Ap… axiosys · bento4 2019-10-10 medium5.5 CVE-2019-16349 Bento4 1.5.1-628 has a NULL pointer dereference in AP4_ByteStream::ReadUI32 in Core/Ap4ByteStream.cpp when called from the AP4_TrunAtom class. axiosys · bento4 2019-09-16 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 high8.8 CVE-2019-15048 An issue was discovered in Bento4 1.5.1.0. axiosys · bento4 2019-08-14 high8.8 CVE-2019-15047 An issue was discovered in Bento4 1.5.1.0. axiosys · bento4 2019-08-14 medium6.5 CVE-2019-13959 In Bento4 1.5.1-627, AP4_DataBuffer::SetDataSize does not handle reallocation failures, leading to a memory copy into a NULL pointer. axiosys · bento4 2019-07-18 high7.5 CVE-2019-13238 An issue was discovered in Bento4 1.5.1.0. axiosys · bento4 2019-07-04

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.