NetSight

Security Dashboard

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

Reset
156 matching advisories · page 5 of 6Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high8.8 CVE-2019-9544 An issue was discovered in Bento4 1.5.1-628. axiosys · bento4 2019-03-01 high8.8 CVE-2019-8382 An issue was discovered in Bento4 1.5.1-628. axiosys · bento4 2019-02-17 high8.8 CVE-2019-8380 An issue was discovered in Bento4 1.5.1-628. axiosys · bento4 2019-02-17 high8.8 CVE-2019-8378 An issue was discovered in Bento4 1.5.1-628. axiosys · bento4 2019-02-17 medium6.5 CVE-2019-7699 A heap-based buffer over-read occurs in AP4_BitStream::WriteBytes in Codecs/Ap4BitStream.cpp in Bento4 v1.5.1-627. axiosys · bento4 2019-02-10 medium6.5 CVE-2019-7698 An issue was discovered in AP4_Array<AP4_CttsTableEntry>::EnsureCapacity in Core/Ap4Array.h in Bento4 1.5.1-627. axiosys · bento4 2019-02-10 medium6.5 CVE-2019-7697 An issue was discovered in Bento4 v1.5.1-627. axiosys · bento4 2019-02-10 medium6.5 CVE-2019-6966 An issue was discovered in Bento4 1.5.1-628. axiosys · bento4 2019-01-25 high7.5 CVE-2019-6132 An issue was discovered in Bento4 v1.5.1-627. axiosys · bento4 2019-01-11 medium6.5 CVE-2018-20659 An issue was discovered in Bento4 1.5.1-627. axiosys · bento4 2019-01-02 medium6.5 CVE-2018-20502 An issue was discovered in Bento4 1.5.1-627. axiosys · bento4 2018-12-26 medium6.5 CVE-2018-20409 An issue was discovered in Bento4 1.5.1-627. axiosys · bento4 2018-12-23 medium6.5 CVE-2018-20408 An issue was discovered in Bento4 1.5.1-627. axiosys · bento4 2018-12-23 medium6.5 CVE-2018-20407 An issue was discovered in Bento4 1.5.1-627. axiosys · bento4 2018-12-23 medium6.5 CVE-2018-20186 An issue was discovered in Bento4 1.5.1-627. axiosys · bento4 2018-12-17 medium6.5 CVE-2018-20095 An issue was discovered in EnsureCapacity in Core/Ap4Array.h in Bento4 1.5.1-627. axiosys · bento4 2018-12-12 high7.5 CVE-2018-14590 An issue has been discovered in Bento4 1.5.1-624. axiosys · bento4 2018-07-24 high8.8 CVE-2018-14589 An issue has been discovered in Bento4 1.5.1-624. axiosys · bento4 2018-07-24 high7.5 CVE-2018-14588 An issue has been discovered in Bento4 1.5.1-624. axiosys · bento4 2018-07-24 high8.8 CVE-2018-14587 An issue has been discovered in Bento4 1.5.1-624. axiosys · bento4 2018-07-24 high8.8 CVE-2018-14586 An issue has been discovered in Bento4 1.5.1-624. axiosys · bento4 2018-07-24 high8.8 CVE-2018-14585 An issue has been discovered in Bento4 1.5.1-624. axiosys · bento4 2018-07-24 high8.8 CVE-2018-14584 An issue has been discovered in Bento4 1.5.1-624. axiosys · bento4 2018-07-24 medium5.5 CVE-2018-14545 There exists one invalid memory read bug in AP4_SampleDescription::GetType() in Ap4SampleDescription.h in Bento4 1.5.1-624, which can allow attackers to cause … axiosys · bento4 2018-07-23 medium5.5 CVE-2018-14544 There exists one invalid memory read bug in AP4_SampleDescription::GetFormat() in Ap4SampleDescription.h in Bento4 1.5.1-624, which can allow attackers to caus… axiosys · bento4 2018-07-23 medium5.5 CVE-2018-14543 There exists one NULL pointer dereference vulnerability in AP4_JsonInspector::AddField in Ap4Atom.cpp in Bento4 1.5.1-624, which can allow attackers to cause a… axiosys · bento4 2018-07-23 critical9.8 CVE-2018-14532 An issue was discovered in Bento4 1.5.1-624. axiosys · bento4 2018-07-23 critical9.8 CVE-2018-14531 An issue was discovered in Bento4 1.5.1-624. axiosys · bento4 2018-07-23 medium6.5 CVE-2018-14445 In Bento4 v1.5.1-624, AP4_File::ParseStream in Ap4File.cpp allows remote attackers to cause a denial of service (infinite loop) via a crafted MP4 file. axiosys · bento4 2018-07-20 high7.5 CVE-2018-13848 An issue has been found in Bento4 1.5.1-624. axiosys · bento4 2018-07-10

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.