NetSight

Security Dashboard

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

Reset
503 matching advisories · page 4 of 17Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium4.4 CVE-2022-21595 Vulnerability in the MySQL Server product of Oracle MySQL (component: C API). oracle · mysql, netapp · oncommand_insight, netapp · oncommand_workflow_automation +1 2022-10-18 high8.8 CVE-2022-39267 Bifrost is a heterogeneous middleware that synchronizes MySQL, MariaDB to Redis, MongoDB, ClickHouse, MySQL and other services for production environments. go · github.com/brokercap/Bifrost 2022-10-18 medium5.5 CVE-2022-38791 In MariaDB before 10.9.2, compress_write in extra/mariabackup/ds_compress.cc does not release data_mutex upon a stream write failure, which allows local users … mariadb · mariadb, fedoraproject · fedora 2022-08-27 high7.5 CVE-2022-32091 MariaDB v10.7 was discovered to contain an use-after-poison in in __interceptor_memset at /libsanitizer/sanitizer_common/sanitizer_common_interceptors.inc. mariadb · mariadb, debian · debian_linux, fedoraproject · fedora 2022-07-01 high7.5 CVE-2022-32089 MariaDB v10.5 to v10.7 was discovered to contain a segmentation fault via the component st_select_lex_unit::exclude_level. mariadb · mariadb, fedoraproject · fedora 2022-07-01 high7.5 CVE-2022-32088 MariaDB v10.2 to v10.7 was discovered to contain a segmentation fault via the component Exec_time_tracker::get_loops/Filesort_tracker::report_use/filesort. mariadb · mariadb, debian · debian_linux 2022-07-01 high7.5 CVE-2022-32087 MariaDB v10.2 to v10.7 was discovered to contain a segmentation fault via the component Item_args::walk_args. mariadb · mariadb, debian · debian_linux 2022-07-01 high7.5 CVE-2022-32086 MariaDB v10.4 to v10.8 was discovered to contain a segmentation fault via the component Item_field::fix_outer_field. mariadb · mariadb 2022-07-01 high7.5 CVE-2022-32085 MariaDB v10.2 to v10.7 was discovered to contain a segmentation fault via the component Item_func_in::cleanup/Item::cleanup_processor. mariadb · mariadb, debian · debian_linux 2022-07-01 high7.5 CVE-2022-32084 MariaDB v10.2 to v10.7 was discovered to contain a segmentation fault via the component sub_select. mariadb · mariadb, debian · debian_linux, fedoraproject · fedora 2022-07-01 high7.5 CVE-2022-32083 MariaDB v10.2 to v10.6.1 was discovered to contain a segmentation fault via the component Item_subselect::init_expr_cache_tracker. mariadb · mariadb, debian · debian_linux 2022-07-01 high7.5 CVE-2022-32082 MariaDB v10.5 to v10.7 was discovered to contain an assertion failure at table->get_ref_count() == 0 in dict0dict.cc. mariadb · mariadb, fedoraproject · fedora 2022-07-01 high7.5 CVE-2022-32081 MariaDB v10.4 to v10.7 was discovered to contain an use-after-poison in prepare_inplace_add_virtual at /storage/innobase/handler/handler0alter.cc. mariadb · mariadb, fedoraproject · fedora 2022-07-01 critical GHSA-2hhc-7wqf-7wgp Malware in azure-arm-mariadb-samples-jsMalware npm · azure-arm-mariadb-samples-js 2022-06-20 critical GHSA-gr36-8944-wjq2 Malware in azure-arm-mariadb-samples-tsMalware npm · azure-arm-mariadb-samples-ts 2022-06-20 medium5.5 CVE-2022-31624 MariaDB Server before 10.7 is vulnerable to Denial of Service. mariadb · mariadb 2022-05-25 medium5.5 CVE-2022-31623 MariaDB Server before 10.7 is vulnerable to Denial of Service. mariadb · mariadb 2022-05-25 medium5.5 CVE-2022-31622 MariaDB Server before 10.7 is vulnerable to Denial of Service. mariadb · mariadb 2022-05-25 medium5.5 CVE-2022-31621 MariaDB Server before 10.7 is vulnerable to Denial of Service. mariadb · mariadb 2022-05-25 medium4.4 CVE-2022-21451 Vulnerability in the MySQL Server product of Oracle MySQL (component: InnoDB). oracle · mysql, netapp · active_iq_unified_manager, netapp · oncommand_insight +3 2022-04-19 medium4.9 CVE-2022-21427 Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: FTS). oracle · mysql, netapp · active_iq_unified_manager, netapp · oncommand_insight +4 2022-04-19 high7.5 CVE-2022-27457 MariaDB Server v10.6.3 and below was discovered to contain an use-after-free in the component my_mb_wc_latin1 at /strings/ctype-latin1.c. mariadb · mariadb 2022-04-14 high7.5 CVE-2022-27456 MariaDB Server v10.6.3 and below was discovered to contain an use-after-free in the component VDec::VDec at /sql/sql_type.cc. mariadb · mariadb, debian · debian_linux 2022-04-14 high7.5 CVE-2022-27455 MariaDB Server v10.6.3 and below was discovered to contain an use-after-free in the component my_wildcmp_8bit_impl at /strings/ctype-simple.c. mariadb · mariadb 2022-04-14 high7.5 CVE-2022-27452 MariaDB Server v10.9 and below was discovered to contain a segmentation fault via the component sql/item_cmpfunc.cc. mariadb · mariadb, debian · debian_linux 2022-04-14 high7.5 CVE-2022-27451 MariaDB Server v10.9 and below was discovered to contain a segmentation fault via the component sql/field_conv.cc. mariadb · mariadb 2022-04-14 high7.5 CVE-2022-27449 MariaDB Server v10.9 and below was discovered to contain a segmentation fault via the component sql/item_func.cc:148. mariadb · mariadb, debian · debian_linux 2022-04-14 high7.5 CVE-2022-27448 There is an Assertion failure in MariaDB Server v10.9 and below via 'node->pcur->rel_pos == BTR_PCUR_ON' at /row/row0mysql.cc. mariadb · mariadb, debian · debian_linux 2022-04-14 high7.5 CVE-2022-27447 MariaDB Server v10.9 and below was discovered to contain a use-after-free via the component Binary_string::free_buffer() at /sql/sql_string.h. mariadb · mariadb, debian · debian_linux 2022-04-14 high7.5 CVE-2022-27446 MariaDB Server v10.9 and below was discovered to contain a segmentation fault via the component sql/item_cmpfunc.h. mariadb · mariadb 2022-04-14

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.