NetSight

Security Dashboard

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

Reset
603 matching advisories · page 18 of 21Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.5 CVE-2021-26388 Improper validation of the BIOS directory may allow for searches to read beyond the directory table copy in RAM, exposing out of bounds memory contents, result… amd · epyc_7232p_firmware, amd · epyc_7302p_firmware, amd · epyc_7402p_firmware +9 2022-05-11 medium5.5 CVE-2021-26378 Insufficient bound checks in the System Management Unit (SMU) may result in access to an invalid address space that could result in denial of service. amd · epyc_7232p_firmware, amd · epyc_7302p_firmware, amd · epyc_7402p_firmware +9 2022-05-11 medium5.5 CVE-2021-26376 Insufficient checks in System Management Unit (SMU) FeatureConfig may result in reenabling features potentially resulting in denial of resources and/or denial … amd · epyc_7232p_firmware, amd · epyc_7302p_firmware, amd · epyc_7402p_firmware +9 2022-05-11 medium5.5 CVE-2021-26375 Insufficient General Purpose IO (GPIO) bounds check in System Management Unit (SMU) may result in access/updates from/to invalid address space that could resul… amd · epyc_7232p_firmware, amd · epyc_7302p_firmware, amd · epyc_7402p_firmware +9 2022-05-11 medium5.5 CVE-2021-26373 Insufficient bound checks in the System Management Unit (SMU) may result in a system voltage malfunction that could result in denial of resources and/or possib… amd · epyc_7232p_firmware, amd · epyc_7302p_firmware, amd · epyc_7402p_firmware +9 2022-05-11 medium5.5 CVE-2021-26372 Insufficient bound checks related to PCIE in the System Management Unit (SMU) may result in access to an invalid address space that could result in denial of s… amd · epyc_7232p_firmware, amd · epyc_7302p_firmware, amd · epyc_7402p_firmware +9 2022-05-11 medium5.5 CVE-2021-26364 Insufficient bounds checking in an SMU mailbox register could allow an attacker to potentially read outside of the SRAM address range which could result in an … amd · epyc_7232p_firmware, amd · epyc_7302p_firmware, amd · epyc_7402p_firmware +9 2022-05-11 medium4.7 CVE-2021-26350 A TOCTOU race condition in SMU may allow for the caller to obtain and manipulate the address of a message port register which may result in a potential denial … amd · epyc_7232p_firmware, amd · epyc_7302p_firmware, amd · epyc_7402p_firmware +9 2022-05-11 medium5.5 CVE-2021-26349 Failure to assign a new report ID to an imported guest may potentially result in an SEV-SNP guest VM being tricked into trusting a dishonest Migration Agent (M… amd · epyc_7763_firmware, amd · epyc_7713p_firmware, amd · epyc_7713_firmware +9 2022-05-11 medium5.5 CVE-2021-26348 Failure to flush the Translation Lookaside Buffer (TLB) of the I/O memory management unit (IOMMU) may lead an IO device to write to memory it should not be abl… amd · epyc_7763_firmware, amd · epyc_7713p_firmware, amd · epyc_7713_firmware +9 2022-05-11 medium4.7 CVE-2021-26347 Failure to validate the integer operand in ASP (AMD Secure Processor) bootloader may allow an attacker to introduce an integer overflow in the L2 directory tab… amd · epyc_7763_firmware, amd · epyc_7713p_firmware, amd · epyc_7713_firmware +9 2022-05-11 medium5.5 CVE-2021-26339 A bug in AMD CPU’s core logic may allow for an attacker, using specific code from an unprivileged VM, to trigger a CPU core hang resulting in a potential denia… amd · epyc_7763_firmware, amd · epyc_7713p_firmware, amd · epyc_7713_firmware +9 2022-05-11 medium6.2 CVE-2021-26390 A malicious or compromised UApp or ABL may coerce the bootloader into corrupting arbitrary memory potentially leading to loss of integrity of data. amd · ryzen_5_2600_firmware, amd · ryzen_5_2600x_firmware, amd · ryzen_5_2700x_firmware +9 2022-05-10 medium5.5 CVE-2021-26352 Insufficient bound checks in System Management Unit (SMU) PCIe Hot Plug table may result in access/updates from/to invalid address space that could result in d… amd · ryzen_5_2600_firmware, amd · ryzen_5_2600x_firmware, amd · ryzen_5_2700x_firmware +9 2022-05-10 medium5.6 CVE-2021-26401 LFENCE/JMP (mitigation V2-2) may not sufficiently mitigate CVE-2017-5715 on some AMD CPUs. amd · athlon_x4_940_firmware, amd · athlon_x4_950_firmware, amd · athlon_x4_970_firmware +9 2022-03-11 medium6.5 CVE-2021-26341 Some AMD CPUs may transiently execute beyond unconditional direct branches, which may potentially result in data leakage. amd · athlon_x4_940_firmware, amd · athlon_x4_950_firmware, amd · athlon_x4_970_firmware +9 2022-03-11 medium6.8 CVE-2021-44850 On Xilinx Zynq-7000 SoC devices, physical modification of an SD boot image allows for a buffer overflow attack in the ROM. amd · xilinx_z-7012s_firmware, amd · xilinx_z-7014s_firmware, amd · xilinx_z-7010_firmware +7 2022-02-10 medium5.5 CVE-2020-12966 AMD EPYC™ Processors contain an information disclosure vulnerability in the Secure Encrypted Virtualization with Encrypted State (SEV-ES) and Secure Encrypted … amd · epyc_7763_firmware, amd · epyc_7713p_firmware, amd · epyc_7713_firmware +9 2022-02-04 medium6.7 CVE-2020-12890 Improper handling of pointers in the System Management Mode (SMM) handling code may allow for a privileged attacker with physical or administrative access to p… amd · amd_generic_encapsulated_software_architecture 2021-12-10 medium5.5 CVE-2021-26337 Insufficient DRAM address validation in System Management Unit (SMU) may result in a DMA read from invalid DRAM address to SRAM resulting in SMU not servicing … amd · epyc_7003_firmware, amd · epyc_7002_firmware, amd · epyc_72f3_firmware +9 2021-11-16 medium5.5 CVE-2021-26336 Insufficient bounds checking in System Management Unit (SMU) may cause invalid memory accesses/updates that could result in SMU hang and subsequent failure to … amd · epyc_7003_firmware, amd · epyc_7002_firmware, amd · epyc_72f3_firmware +9 2021-11-16 medium5.5 CVE-2021-26330 AMD System Management Unit (SMU) may experience a heap-based overflow which may result in a loss of resources. amd · epyc_7003_firmware, amd · epyc_7002_firmware, amd · epyc_7001_firmware +9 2021-11-16 medium5.5 CVE-2021-26327 Insufficient validation of guest context in the SNP Firmware could lead to a potential loss of guest confidentiality. amd · epyc_7003_firmware, amd · epyc_72f3_firmware, amd · epyc_7313_firmware +9 2021-11-16 medium5.5 CVE-2021-26325 Insufficient input validation in the SNP_GUEST_REQUEST command may lead to a potential data abort error and a denial of service. amd · epyc_7232p_firmware, amd · epyc_7763_firmware, amd · epyc_7713p_firmware +9 2021-11-16 medium5.5 CVE-2021-26321 Insufficient ID command validation in the SEV Firmware may allow a local authenticated attacker to perform a denial of service of the PSP. amd · epyc_7601_firmware, amd · epyc_7551p_firmware, amd · epyc_7551_firmware +9 2021-11-16 medium5.5 CVE-2021-26320 Insufficient validation of the AMD SEV Signing Key (ASK) in the SEND_START command in the SEV Firmware may allow a local authenticated attacker to perform a de… amd · epyc_7601_firmware, amd · epyc_7551p_firmware, amd · epyc_7551_firmware +9 2021-11-16 medium5.5 CVE-2020-12954 A side effect of an integrated chipset option may be able to be used by an attacker to bypass SPI ROM protections, allowing unauthorized SPI ROM modification. amd · epyc_7003_firmware, amd · epyc_7002_firmware, amd · epyc_7001_firmware +9 2021-11-16 medium5.5 CVE-2021-26329 AMD System Management Unit (SMU) may experience an integer overflow when an invalid length is provided which may result in a potential loss of resources. amd · epyc_7601_firmware, amd · epyc_7551p_firmware, amd · epyc_7551_firmware +9 2021-11-16 medium5.5 CVE-2021-26312 Failure to flush the Translation Lookaside Buffer (TLB) of the I/O memory management unit (IOMMU) may lead an IO device to write to memory it should not be abl… amd · epyc_7601_firmware, amd · epyc_7551p_firmware, amd · epyc_7551_firmware +9 2021-11-16 medium5.5 CVE-2020-12960 AMD Graphics Driver for Windows 10, amdfender.sys may improperly handle input validation on InputBuffer which may result in a denial of service (DoS). amd · radeon_software 2021-11-15

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.