NetSight

Security Dashboard

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

Reset
603 matching advisories · page 16 of 21Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.1 CVE-2023-20533 Insufficient DRAM address validation in System Management Unit (SMU) may allow an attacker to read/write from/to an invalid DRAM address, potentially resulting… amd · epyc_7232p_firmware, amd · epyc_7252_firmware, amd · epyc_7262_firmware +9 2023-11-14 medium6.7 CVE-2021-46774 Insufficient DRAM address validation in System Management Unit (SMU) may allow an attacker to read/write from/to an invalid DRAM address, potentially resulting… amd · epyc_7001_firmware, amd · epyc_7251_firmware, amd · epyc_7261_firmware +9 2023-11-14 medium6.1 CVE-2021-46758 Insufficient validation of SPI flash addresses in the ASP (AMD Secure Processor) bootloader may allow an attacker to read data in memory mapped beyond SPI flas… amd · ryzen_7_5700g_firmware, amd · ryzen_7_5700ge_firmware, amd · ryzen_5_5600g_firmware +9 2023-11-14 medium5.5 CVE-2021-46748 Insufficient bounds checking in the ASP (AMD Secure Processor) may allow an attacker to access memory outside the bounds of what is permissible to a TA (Truste… intel · radeon_rx_vega_m_firmware, amd · radeon_software, amd · radeon_rx_vega_56_firmware +3 2023-11-14 medium4.3 CVE-2023-5296 A vulnerability was found in Xinhu RockOA 1.1/2.3.2/15.X3amdi and classified as problematic. rockoa · rockoa 2023-09-29 medium5.3 CVE-2023-44216 PVRIC (PowerVR Image Compression) on Imagination 2018 and later GPU devices offers software-transparent compression that enables cross-origin pixel-stealing at… canonical · ubuntu_linux, amd · ryzen_7_4800u, intel · core_i7-10510u +9 2023-09-27 medium5.5 CVE-2023-20597 Improper initialization of variables in the DXE driver may allow a privileged user to leak sensitive information via local access. amd · ryzen_3_3100_firmware, amd · ryzen_3_3200g_firmware, amd · ryzen_3_3200ge_firmware +9 2023-09-20 medium4.4 CVE-2023-20594 Improper initialization of variables in the DXE driver may allow a privileged user to leak sensitive information via local access. amd · epyc_7003_firmware, amd · epyc_72f3_firmware, amd · epyc_7313_firmware +9 2023-09-20 medium5.3 CVE-2023-4155 A flaw was found in KVM AMD Secure Encrypted Virtualization (SEV) in the Linux kernel. linux · linux_kernel, redhat · enterprise_linux, fedoraproject · fedora 2023-09-13 medium6.7 CVE-2023-20564 Insufficient validation in the IOCTL (Input Output Control) input buffer in AMD Ryzen™ Master may permit a privileged attacker to perform memory reads/writes p… amd · ryzen_master, amd · ryzen_master_monitoring_sdk 2023-08-15 medium4.4 CVE-2023-20560 Insufficient validation of the IOCTL (Input Output Control) input buffer in AMD Ryzen™ Master may allow a privileged attacker to provide a null value potential… amd · ryzen_master, amd · ryzen_master_monitoring_sdk 2023-08-15 medium6.8 CVE-2023-20589 An attacker with specialized hardware and physical access to an impacted device may be able to perform a voltage fault injection attack resulting in compromise… amd · ryzen_5_pro_3400g_firmware, amd · ryzen_5_3400g_firmware, amd · ryzen_5_pro_3400ge_firmware +9 2023-08-08 medium5.5 CVE-2023-20588 A division-by-zero error on some AMD processors can potentially return speculative data resulting in loss of confidentiality. debian · debian_linux, amd · epyc_7351p_firmware, amd · epyc_7401p_firmware +9 2023-08-08 medium4.7 CVE-2023-20569 A side channel vulnerability on some of the AMD CPUs may allow an attacker to influence the return address prediction. fedoraproject · fedora, debian · debian_linux, amd · ryzen_9_5950x_firmware +9 2023-08-08 medium5.5 CVE-2023-20561 Insufficient validation of the IOCTL (Input Output Control) input buffer in AMD μProf may allow an authenticated user to send an arbitrary address potentially … amd · amd_uprof 2023-08-08 medium5.5 CVE-2023-20556 Insufficient validation of the IOCTL (Input Output Control) input buffer in AMD μProf may allow an authenticated user to send an arbitrary buffer potentially r… amd · amd_uprof 2023-08-08 medium4.7 CVE-2023-20583 A potential power side-channel vulnerability in AMD processors may allow an authenticated attacker to monitor the CPU power consumption as the data in a cache … amd · * 2023-08-01 medium5.5 CVE-2023-20593 An issue in “Zen 2” CPUs, under specific microarchitectural circumstances, may allow an attacker to potentially access sensitive information. xen · xen, debian · debian_linux, amd · ryzen_3_3100_firmware +9 2023-07-24 medium6.5 CVE-2023-20575 A potential power side-channel vulnerability in some AMD processors may allow an authenticated attacker to use the power reporting functionality to monitor a p… amd · epyc_7251_firmware, amd · epyc_7281_firmware, amd · epyc_7301_firmware +9 2023-07-11 medium5.5 CVE-2023-3357 A NULL pointer dereference flaw was found in the Linux kernel AMD Sensor Fusion Hub driver. linux · linux_kernel 2023-06-28 medium5.9 CVE-2021-46792 Time-of-check Time-of-use (TOCTOU) in the BIOS2PSP command may allow an attacker with a malicious BIOS to create a race condition causing the ASP bootloader to… amd · ryzen_5300g_firmware, amd · ryzen_5300ge_firmware, amd · ryzen_5500_firmware +9 2023-05-09 medium6.1 CVE-2021-46759 Improper syscall input validation in AMD TEE (Trusted Execution Environment) may allow an attacker with physical access and control of a Uapp that runs under t… amd · ryzen_5300g_firmware, amd · ryzen_5300ge_firmware, amd · ryzen_5500_firmware +9 2023-05-09 medium6.8 CVE-2021-46775 Improper input validation in ABL may enable an attacker with physical access, to perform arbitrary memory overwrites, potentially leading to a loss of integrit… amd · epyc_72f3_firmware, amd · epyc_7313_firmware, amd · epyc_7313p_firmware +9 2023-05-09 medium5.5 CVE-2021-26371 A compromised or malicious ABL or UApp could send a SHA256 system call to the bootloader, which may result in exposure of ASP memory to userspace, potentially … amd · epyc_7773x_firmware, amd · epyc_7763_firmware, amd · epyc_7713p_firmware +9 2023-05-09 medium5.5 CVE-2021-26354 Insufficient bounds checking in ASP may allow an attacker to issue a system call from a compromised ABL which may cause arbitrary memory values to be initializ… amd · epyc_7773x_firmware, amd · epyc_7763_firmware, amd · epyc_7713p_firmware +9 2023-05-09 medium4.7 CVE-2022-27672 When SMT is enabled, certain AMD processors may speculatively execute instructions using a target from the sibling thread after an SMT mode switch potentially … amd · athlon_x4_750_firmware, amd · athlon_x4_760k_firmware, amd · athlon_x4_830_firmware +9 2023-03-01 medium5.5 CVE-2011-10001 A vulnerability was found in iamdroppy phoenixcf. phoenixcf_project · phoenixcf 2023-01-18 medium5.3 CVE-2023-20532 Insufficient input validation in the SMU may allow an attacker to improperly lock resources, potentially resulting in a denial of service. amd · epyc_7h12_firmware, amd · epyc_7f72_firmware, amd · epyc_7f52_firmware +9 2023-01-11 medium6.5 CVE-2023-20527 Improper syscall input validation in the ASP Bootloader may allow a privileged attacker to read memory out-of-bounds, potentially leading to a denial-of-servic… amd · epyc_7h12_firmware, amd · epyc_7f72_firmware, amd · epyc_7f52_firmware +9 2023-01-11 medium6.5 CVE-2023-20525 Insufficient syscall input validation in the ASP Bootloader may allow a privileged attacker to read memory outside the bounds of a mapped register potentially … amd · epyc_7h12_firmware, amd · epyc_7f72_firmware, amd · epyc_7f52_firmware +9 2023-01-11

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.