NetSight

Security Dashboard

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

Reset
661 matching advisories · page 11 of 23Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.5 CVE-2023-23919 A cryptographic vulnerability exists in Node.js <19.2.0, <18.14.1, <16.19.1, <14.21.3 that in some cases did does not clear the OpenSSL error stack after opera… nodejs · node.js 2023-02-23 high GHSA-344m-qcjq-xgrf Vulnerable OpenSSL included in sgx-dcap-quote-verify-python pip · sgx-dcap-quote-verify-python 2023-02-14 critical9.1 CVE-2022-4203 openssl-src contains Read Buffer Overflow in X.509 Name Constraint rust · openssl-src 2023-02-08 high7.5 CVE-2023-0401 A NULL pointer can be dereferenced when signatures are being verified on PKCS7 signed or signedAndEnveloped data. rust · openssl-src 2023-02-08 high7.4 CVE-2023-0286 There is a type confusion vulnerability relating to X.400 address processing inside an X.509 GeneralName. pip · cryptography, rust · openssl-src 2023-02-08 high7.5 CVE-2023-0217 An invalid pointer dereference on read can be triggered when an application tries to check a malformed DSA public key by the EVP_PKEY_public_check() function. rust · openssl-src 2023-02-08 high7.5 CVE-2023-0216 An invalid pointer dereference on read can be triggered when an application tries to load malformed PKCS7 data with the d2i_PKCS7(), d2i_PKCS7_bio() or d2i_PKC… rust · openssl-src 2023-02-08 high7.5 CVE-2023-0215 The public API function BIO_new_NDEF is a helper function used for streaming ASN.1 data via a BIO. rust · openssl-src 2023-02-08 high7.5 CVE-2022-4450 The function PEM_read_bio_ex() reads a PEM file from a BIO and parses and decodes the "name" (e.g. rust · openssl-src 2023-02-08 medium5.9 CVE-2022-4304 A timing based side channel exists in the OpenSSL RSA Decryption implementation which could be sufficient to recover a plaintext across a network in a Bleichen… rust · openssl-src 2023-02-08 high7.5 CVE-2009-4123 jruby-openssl gem for JRuby fails to do proper certificate validation rubygems · jruby-openssl 2023-01-19 high7.8 CVE-2022-0517 Mozilla VPN can load an OpenSSL configuration file from an unsecured directory. mozilla · vpn 2022-12-22 high7.5 CVE-2022-3996 Denial of service by double-checked locking in openssl-src rust · openssl-src 2022-12-13 medium GHSA-39hc-v87j-747x Vulnerable OpenSSL included in cryptography wheels pip · cryptography 2022-11-02 critical9.8 CVE-2022-3602 A buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint checking. rust · openssl-src 2022-11-01 high7.5 CVE-2022-3786 X.509 Email Address Variable Length Buffer Overflow rust · openssl-src 2022-11-01 high7.5 CVE-2022-3358 OpenSSL supports creating a custom cipher via the legacy EVP_CIPHER_meth_new() function and associated function calls. rust · openssl-src 2022-10-11 medium5.3 CVE-2022-32222 A cryptographic vulnerability exists on Node.js on linux in versions of 18.x prior to 18.40.0 which allowed a default path for openssl.cnf that might be access… nodejs · node.js, siemens · sinec_ins 2022-07-14 critical9.1 CVE-2014-8164 A insecure configuration for certificate verification (http.verify_mode = OpenSSL::SSL::VERIFY_NONE) may lead to verification bypass in Red Hat CloudForms 5.x. redhat · cloudforms_management_engine 2022-07-06 high7.5 CVE-2022-2097 AES OCB mode for 32-bit x86 platforms using the AES-NI assembly optimised implementation will not encrypt the entirety of the data under some circumstances. rust · openssl-src 2022-07-05 critical9.8 CVE-2022-2274 The OpenSSL 3.0.4 release introduced a serious bug in the RSA implementation for X86_64 CPUs supporting the AVX512IFMA instructions. rust · openssl-src 2022-07-01 critical9.8 CVE-2022-2068 In addition to the c_rehash shell command injection identified in CVE-2022-1292, further circumstances where the c_rehash script does not properly sanitise she… openssl · openssl, debian · debian_linux, fedoraproject · fedora +10 2022-06-21 high7.8 CVE-2022-25153 The ITarian Endpoint Manage Communication Client, prior to version 6.43.41148.21120, is compiled using insecure OpenSSL settings. itarian · endpoint_manager_communication_client 2022-06-09 medium5.9 CVE-2022-29242 GOST engine is a reference implementation of the Russian GOST crypto algorithms for OpenSSL. gost_engine_project · gost_engine 2022-05-24 high7.5 CVE-2022-1473 The OPENSSL_LH_flush() function, which empties a hash table, contains a bug that breaks reuse of the memory occuppied by the removed hash table entries. rust · openssl-src 2022-05-03 medium5.9 CVE-2022-1434 The OpenSSL 3.0 implementation of the RC4-MD5 ciphersuite incorrectly uses the AAD data as the MAC key. rust · openssl-src 2022-05-03 medium5.3 CVE-2022-1343 The function `OCSP_basic_verify` verifies the signer certificate on an OCSP response. rust · openssl-src 2022-05-03 critical9.8 CVE-2022-1292 The c_rehash script does not properly sanitise shell metacharacters to prevent command injection. siemens · brownfield_connectivity_gateway, openssl · openssl, debian · debian_linux +10 2022-05-03 medium6.6 CVE-2022-28198 NVIDIA Omniverse Nucleus and Cache contain a vulnerability in its configuration of OpenSSL, where an attacker with physical access to the system can cause arbi… nvidia · omniverse_cache, nvidia · omniverse_nucleus 2022-04-29 high7.8 CVE-2022-29505 Due to build misconfiguration in openssl dependency, LINE for Windows before 7.8 is vulnerable to DLL injection that could lead to privilege escalation. linecorp · line 2022-04-27

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.