NetSight

Security Dashboard

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

Reset
603 matching advisories · page 17 of 21Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.7 CVE-2023-20523 TOCTOU in the ASP may allow a physical attacker to write beyond the buffer bounds, potentially leading to a loss of integrity or denial of service. amd · epyc_7h12_firmware, amd · epyc_7f72_firmware, amd · epyc_7f52_firmware +9 2023-01-11 medium5.3 CVE-2022-23814 Failure to validate addresses provided by software to BIOS commands may result in a potential loss of integrity of guest memory in a confidential compute envir… amd · milanpi-sp3_firmware 2023-01-11 medium5.3 CVE-2022-23813 The software interfaces to ASP and SMU may not enforce the SNP memory security policy resulting in a potential loss of integrity of guest memory in a confident… amd · milanpi-sp3_firmware, amd · romepi_firmware 2023-01-11 medium4.7 CVE-2021-46795 A TOCTOU (time-of-check to time-of-use) vulnerability exists where an attacker may use a compromised BIOS to cause the TEE OS to read memory out of bounds that… amd · comboam4v2_pi_firmware, amd · renoirpi-fp6_firmware, amd · cezannepi-fp6_firmware 2023-01-11 medium5.5 CVE-2021-46791 Insufficient input validation during parsing of the System Management Mode (SMM) binary may allow a maliciously crafted SMM executable binary to corrupt Dynami… amd · milanpi_firmware 2023-01-11 medium5.5 CVE-2021-46768 Insufficient input validation in SEV firmware may allow an attacker to perform out-of-bounds memory reads within the ASP boot loader, potentially leading to a … amd · romepi_firmware, amd · milanpi_firmware 2023-01-11 medium6.1 CVE-2021-46767 Insufficient input validation in the ASP may allow an attacker with physical access, unauthorized write access to memory potentially leading to a loss of integ… amd · romepi_firmware, amd · milanpi_firmware 2023-01-11 medium5.5 CVE-2021-26407 A randomly generated Initialization Vector (IV) may lead to a collision of IVs with the same key potentially resulting in information disclosure. amd · romepi_firmware 2023-01-11 medium5.5 CVE-2021-26404 Improper input validation and bounds checking in SEV firmware may leak scratch buffer bytes leading to potential information disclosure. amd · epyc_7003_firmware, amd · epyc_7313_firmware, amd · epyc_7313p_firmware +9 2023-01-11 medium6.5 CVE-2021-26403 Insufficient checks in SEV may lead to a malicious hypervisor disclosing the launch secret potentially resulting in compromise of VM confidentiality. amd · epyc_7001_firmware, amd · epyc_7251_firmware, amd · epyc_7261_firmware +9 2023-01-11 medium4.4 CVE-2021-26396 Insufficient validation of address mapping to IO in ASP (AMD Secure Processor) may result in a loss of memory integrity in the SNP guest. amd · epyc_7003_firmware, amd · epyc_72f3_firmware, amd · epyc_7313_firmware +9 2023-01-11 medium5.5 CVE-2021-26355 Insufficient fencing and checks in System Management Unit (SMU) may result in access to invalid message port registers that could result in a potential denial-… amd · epyc_7003_firmware, amd · epyc_72f3_firmware, amd · epyc_7313_firmware +9 2023-01-11 medium5.5 CVE-2021-26346 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 · ryzen_3_3100_firmware, amd · ryzen_3_3200g_firmware, amd · ryzen_3_3200u_firmware +9 2023-01-11 medium5.5 CVE-2021-26343 Insufficient validation in ASP BIOS and DRTM commands may allow malicious supervisor x86 software to disclose the contents of sensitive memory which may result… amd · epyc_7003_firmware, amd · epyc_72f3_firmware, amd · epyc_7313_firmware +9 2023-01-11 medium4.4 CVE-2021-26328 Failure to verify the mode of CPU execution at the time of SNP_INIT may lead to a potential loss of memory integrity for SNP guests. amd · epyc_7003_firmware, amd · epyc_72f3_firmware, amd · epyc_7313_firmware +9 2023-01-11 medium5.5 CVE-2022-23824 IBPB may not prevent return branch predictions from being specified by pre-IBPB branch targets leading to a potential information disclosure. xen · xen, amd · athlon_x4_750_firmware, amd · athlon_x4_760k_firmware +9 2022-11-09 medium5.5 CVE-2021-26393 Insufficient memory cleanup in the AMD Secure Processor (ASP) Trusted Execution Environment (TEE) may allow an authenticated attacker with privileges to genera… amd · enterprise_driver, amd · radeon_pro_software, amd · radeon_software +9 2022-11-09 medium5.5 CVE-2022-3344 A flaw was found in the KVM's AMD nested virtualization (SVM). linux · linux_kernel 2022-10-25 medium5.6 CVE-2021-46778 Execution unit scheduler contention may lead to a side channel vulnerability found on AMD CPU microarchitectures codenamed “Zen 1”, “Zen 2” and “Zen 3” that us… amd · athlon_3050ge_firmware, amd · athlon_3150g_firmware, amd · athlon_3150ge_firmware +9 2022-08-10 medium6.5 CVE-2022-23825 Aliases in the branch predictor may cause some AMD processors to predict the wrong branch type potentially leading to information disclosure. debian · debian_linux, fedoraproject · fedora, amd · athlon_x4_750_firmware +9 2022-07-14 medium4.4 CVE-2021-26382 An attacker with root account privileges can load any legitimately signed firmware image into the Audio Co-Processor (ACP,) irrespective of the respective sign… amd · ryzen_7_5700g_firmware, amd · ryzen_7_5700ge_firmware, amd · ryzen_5_5600g_firmware +9 2022-07-14 medium6.5 CVE-2022-29900 Mis-trained branch predictions for return instructions may allow arbitrary speculative code execution under certain microarchitecture-dependent conditions. debian · debian_linux, fedoraproject · fedora, xen · xen +9 2022-07-12 medium6.5 CVE-2022-23823 A potential vulnerability in some AMD processors using frequency scaling may allow an authenticated attacker to execute a timing attack to potentially enable i… amd · athlon_x4_750_firmware, amd · athlon_x4_760k_firmware, amd · athlon_x4_830_firmware +9 2022-06-15 medium4.4 CVE-2022-20182 In handle_ramdump of pixel_loader.c, there is a possible way to create a ramdump of non-secure memory due to a missing permission check. google · android 2022-06-15 medium4.4 CVE-2021-26368 Insufficient check of the process type in Trusted OS (TOS) may allow an attacker with privileges to enable a lesser privileged process to unmap memory owned by… amd · ryzen_3_2200u_firmware, amd · ryzen_3_2300u_firmware, amd · ryzen_3_3100_firmware +9 2022-05-12 medium4.4 CVE-2021-26363 A malicious or compromised UApp or ABL could potentially change the value that the ASP uses for its reserved DRAM, to one outside of the fenced area, potential… amd · radeon_software, amd · ryzen_3_3100_firmware, amd · ryzen_3_3300g_firmware +9 2022-05-12 medium5.5 CVE-2021-26361 A malicious or compromised User Application (UApp) or AGESA Boot Loader (ABL) could be used by an attacker to exfiltrate arbitrary memory from the ASP stage 2 … amd · radeon_software, amd · ryzen_3_2200u_firmware, amd · ryzen_3_2300u_firmware +9 2022-05-12 medium5.5 CVE-2021-26351 Insufficient DRAM address validation in System Management Unit (SMU) may result in a DMA (Direct Memory Access) read/write from/to invalid DRAM address that co… amd · ryzen_3_3100_firmware, amd · ryzen_3_3300g_firmware, amd · ryzen_3_3300x_firmware +9 2022-05-12 medium6.5 CVE-2021-46744 An attacker with access to a malicious hypervisor may be able to infer data values used in a SEV guest on AMD CPUs by monitoring ciphertext values over time. amd · epyc_7001_firmware, amd · epyc_7002_firmware, amd · epyc_7003_firmware +9 2022-05-11 medium4.0 CVE-2021-26400 AMD processors may speculatively re-order load instructions which can result in stale data being observed when multiple processors are operating on shared memo… amd · cpu 2022-05-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.