NetSight

Security Dashboard

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

Reset
110 matching advisories · page 2 of 4Index updated 10 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium5.5 CVE-2022-24350 An issue was discovered in IhisiSmm in Insyde InsydeH2O with kernel 5.0 through 5.5. insyde · insydeh2o 2023-04-12 high8.8 CVE-2023-22613 An issue was discovered in IhisiSmm in Insyde InsydeH2O with kernel 5.0 through 5.5. insyde · insydeh2o 2023-04-11 high8.4 CVE-2023-22615 An issue was discovered in IhisiSmm in Insyde InsydeH2O with kernel 5.0 through 5.5. insyde · insydeh2o 2023-04-11 high8.8 CVE-2023-22614 An issue was discovered in ChipsetSvcSmm in Insyde InsydeH2O with kernel 5.0 through 5.5. insyde · insydeh2o 2023-04-11 high8.8 CVE-2023-22612 An issue was discovered in IhisiSmm in Insyde InsydeH2O with kernel 5.0 through 5.5. insyde · insydeh2o 2023-04-11 high7.0 CVE-2022-32477 An issue was discovered in Insyde InsydeH2O with kernel 5.0 through 5.5. insyde · insydeh2o 2023-02-15 high7.0 CVE-2022-32475 An issue was discovered in Insyde InsydeH2O with kernel 5.0 through 5.5. insyde · insydeh2o 2023-02-15 high7.0 CVE-2022-32469 An issue was discovered in Insyde InsydeH2O with kernel 5.0 through 5.5. insyde · insydeh2o 2023-02-15 high7.0 CVE-2022-32953 An issue was discovered in Insyde InsydeH2O with kernel 5.0 through 5.5. insyde · insydeh2o 2023-02-15 high7.0 CVE-2022-32476 An issue was discovered in Insyde InsydeH2O with kernel 5.0 through 5.5. insyde · insydeh2o 2023-02-15 high7.0 CVE-2022-32473 An issue was discovered in Insyde InsydeH2O with kernel 5.0 through 5.5. insyde · insydeh2o 2023-02-15 high7.0 CVE-2022-32470 An issue was discovered in Insyde InsydeH2O with kernel 5.0 through 5.5. insyde · insydeh2o 2023-02-15 high7.0 CVE-2022-32955 An issue was discovered in Insyde InsydeH2O with kernel 5.0 through 5.5. insyde · insydeh2o 2023-02-15 high7.0 CVE-2022-32954 An issue was discovered in Insyde InsydeH2O with kernel 5.1 through 5.5. insyde · insydeh2o 2023-02-15 high7.0 CVE-2022-32478 An issue was discovered in Insyde InsydeH2O with kernel 5.0 through 5.5. insyde · insydeh2o 2023-02-15 high7.0 CVE-2022-32474 An issue was discovered in Insyde InsydeH2O with kernel 5.0 through 5.5. insyde · insydeh2o 2023-02-15 high7.0 CVE-2022-32471 An issue was discovered in IhisiSmm in Insyde InsydeH2O with kernel 5.0 through 5.5. insyde · insydeh2o 2023-02-15 high8.2 CVE-2022-36337 An issue was discovered in Insyde InsydeH2O with kernel 5.0 through 5.5. insyde · kernel 2022-11-23 high7.8 CVE-2022-35407 An issue was discovered in Insyde InsydeH2O with kernel 5.0 through 5.5. insyde · kernel 2022-11-22 medium6.8 CVE-2022-35897 An stack buffer overflow vulnerability leads to arbitrary code execution issue was discovered in Insyde InsydeH2O with kernel 5.0 through 5.5. insyde · kernel 2022-11-21 high8.2 CVE-2022-29279 Use of a untrusted pointer allows tampering with SMRAM and OS memory in SdHostDriver and SdMmcDevice Use of a untrusted pointer allows tampering with SMRAM and… insyde · kernel 2022-11-15 high8.2 CVE-2022-29278 Incorrect pointer checks within the NvmExpressDxe driver can allow tampering with SMRAM and OS memory Incorrect pointer checks within the NvmExpressDxe driver … insyde · kernel 2022-11-15 high8.2 CVE-2022-29276 SMI functions in AhciBusDxe use untrusted inputs leading to corruption of SMRAM. insyde · kernel 2022-11-15 high8.2 CVE-2022-30772 Manipulation of the input address in PnpSmm function 0x52 could be used by malware to overwrite SMRAM or OS kernel memory. insyde · kernel 2022-11-15 high8.2 CVE-2022-30771 Initialization function in PnpSmm could lead to SMRAM corruption when using subsequent PNP SMI functions Initialization function in PnpSmm could lead to SMRAM … insyde · kernel 2022-11-15 high7.5 CVE-2022-30283 In UsbCoreDxe, tampering with the contents of the USB working buffer using DMA while certain USB transactions are in process leads to a TOCTOU problem that cou… insyde · kernel 2022-11-15 high8.2 CVE-2022-29275 In UsbCoreDxe, untrusted input may allow SMRAM or OS memory tampering Use of untrusted pointers could allow OS or SMRAM memory tampering leading to escalation … insyde · kernel 2022-11-15 medium6.4 CVE-2022-33986 DMA attacks on the parameter buffer used by the VariableRuntimeDxe software SMI handler could lead to a TOCTOU attack. insyde · kernel 2022-11-15 high7.0 CVE-2022-33985 DMA transactions which are targeted at input buffers used for the NvmExpressDxe software SMI handler could cause SMRAM corruption through a TOCTOU attack. insyde · kernel 2022-11-15 high7.0 CVE-2022-33984 DMA transactions which are targeted at input buffers used for the SdMmcDevice software SMI handler could cause SMRAM corruption through a TOCTOU attack. insyde · kernel 2022-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.