NetSight

Security Dashboard

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

Reset
54 matching advisories · page 2 of 2Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.8 CVE-2019-13104 In Das U-Boot versions 2016.11-rc1 through 2019.07-rc4, an underflow can cause memcpy() to overwrite a very large amount of data (including the whole stack) wh… denx · u-boot, opensuse · leap 2019-08-06 critical9.8 CVE-2019-14204 An issue was discovered in Das U-Boot through 2019.07. denx · u-boot 2019-07-31 critical9.8 CVE-2019-14203 An issue was discovered in Das U-Boot through 2019.07. denx · u-boot 2019-07-31 critical9.8 CVE-2019-14202 An issue was discovered in Das U-Boot through 2019.07. denx · u-boot 2019-07-31 critical9.8 CVE-2019-14201 An issue was discovered in Das U-Boot through 2019.07. denx · u-boot 2019-07-31 critical9.8 CVE-2019-14200 An issue was discovered in Das U-Boot through 2019.07. denx · u-boot 2019-07-31 critical9.8 CVE-2019-14199 An issue was discovered in Das U-Boot through 2019.07. denx · u-boot 2019-07-31 critical9.8 CVE-2019-14198 An issue was discovered in Das U-Boot through 2019.07. denx · u-boot 2019-07-31 critical9.1 CVE-2019-14197 An issue was discovered in Das U-Boot through 2019.07. denx · u-boot 2019-07-31 critical9.8 CVE-2019-14196 An issue was discovered in Das U-Boot through 2019.07. denx · u-boot 2019-07-31 critical9.8 CVE-2019-14195 An issue was discovered in Das U-Boot through 2019.07. denx · u-boot 2019-07-31 critical9.8 CVE-2019-14194 An issue was discovered in Das U-Boot through 2019.07. denx · u-boot 2019-07-31 critical9.8 CVE-2019-14193 An issue was discovered in Das U-Boot through 2019.07. denx · u-boot 2019-07-31 critical9.8 CVE-2019-14192 An issue was discovered in Das U-Boot through 2019.07. denx · u-boot 2019-07-31 high7.1 CVE-2019-13103 A crafted self-referential DOS partition table will cause all Das U-Boot versions through 2019.07-rc4 to infinitely recurse, causing the stack to grow infinite… denx · u-boot 2019-07-29 critical9.8 CVE-2019-11059 Das U-Boot 2016.11-rc1 through 2019.04 mishandles the ext4 64-bit extension, resulting in a buffer overflow. denx · u-boot 2019-05-10 medium5.9 CVE-2019-11690 gen_rand_uuid in lib/uuid.c in Das U-Boot v2014.04 through v2019.04 lacks an srand call, which allows attackers to determine UUID values in scenarios where CON… denx · u-boot 2019-05-03 high7.0 CVE-2018-3968 An exploitable vulnerability exists in the verified boot protection of the Das U-Boot from version 2013.07-rc1 to 2014.07-rc2. denx · u-boot 2019-03-21 high7.8 CVE-2018-18440 DENX U-Boot through 2018.09-rc1 has a locally exploitable buffer overflow via a crafted kernel image because filesystem loading is mishandled. denx · u-boot 2018-11-20 critical9.8 CVE-2018-18439 DENX U-Boot through 2018.09-rc1 has a remotely exploitable buffer overflow via a malicious TFTP server because TFTP traffic is mishandled. denx · u-boot 2018-11-20 medium6.4 CVE-2017-3226 Das U-Boot is a device bootloader that can read its configuration from an AES encrypted file. denx · u-boot 2018-07-24 medium4.6 CVE-2017-3225 Das U-Boot is a device bootloader that can read its configuration from an AES encrypted file. denx · u-boot 2018-07-24 medium5.5 CVE-2018-1000205 U-Boot contains a CWE-20: Improper Input Validation vulnerability in Verified boot signature validation that can result in Bypass verified boot. denx · u-boot 2018-06-26 high8.8 CVE-2018-12519 An issue was discovered in ShopNx through 2017-11-17. codenx · shopnx 2018-06-19

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.