NetSight

Security Dashboard

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

Reset
173 matching advisories · page 5 of 6Index updated 3 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.5 CVE-2022-25638 In wolfSSL before 5.2.0, certificate validation may be bypassed during attempted authentication by a TLS 1.3 client to a TLS 1.3 server. wolfssl · wolfssl 2022-02-24 critical9.1 CVE-2022-23408 wolfSSL 5.x before 5.1.1 uses non-random IV values in certain situations. wolfssl · wolfssl 2022-01-18 medium5.5 CVE-2021-45939 wolfSSL wolfMQTT 1.9 has a heap-based buffer overflow in MqttClient_DecodePacket (called from MqttClient_WaitType and MqttClient_Subscribe). wolfssl · wolfmqtt 2022-01-01 medium5.5 CVE-2021-45938 wolfSSL wolfMQTT 1.9 has a heap-based buffer overflow in MqttClient_DecodePacket (called from MqttClient_WaitType and MqttClient_Unsubscribe). wolfssl · wolfmqtt 2022-01-01 medium5.5 CVE-2021-45937 wolfSSL wolfMQTT 1.9 has a heap-based buffer overflow in MqttClient_DecodePacket (called from MqttClient_WaitType and MqttClient_Connect). wolfssl · wolfmqtt 2022-01-01 medium5.5 CVE-2021-45936 wolfSSL wolfMQTT 1.9 has a heap-based buffer overflow in MqttDecode_Disconnect (called from MqttClient_DecodePacket and MqttClient_WaitType). wolfssl · wolfmqtt 2022-01-01 medium5.5 CVE-2021-45934 wolfSSL wolfMQTT 1.9 has a heap-based buffer overflow in MqttClient_DecodePacket (called from MqttClient_HandlePacket and MqttClient_WaitType). wolfssl · wolfmqtt 2022-01-01 medium5.5 CVE-2021-45933 wolfSSL wolfMQTT 1.9 has a heap-based buffer overflow (8 bytes) in MqttDecode_Publish (called from MqttClient_DecodePacket and MqttClient_HandlePacket). wolfssl · wolfmqtt 2022-01-01 medium5.5 CVE-2021-45932 wolfSSL wolfMQTT 1.9 has a heap-based buffer overflow (4 bytes) in MqttDecode_Publish (called from MqttClient_DecodePacket and MqttClient_HandlePacket). wolfssl · wolfmqtt 2022-01-01 medium5.9 CVE-2021-38597 wolfSSL before 4.8.1 incorrectly skips OCSP verification in certain situations of irrelevant response data that contains the NoCheck extension. wolfssl · wolfssl 2021-08-12 critical9.8 CVE-2021-37155 wolfSSL 4.6.x through 4.7.x before 4.8.0 does not produce a failure outcome when the serial number in an OCSP request differs from the serial number in the OCS… wolfssl · wolfssl 2021-07-21 medium4.9 CVE-2021-24116 In wolfSSL through 4.6.0, a side-channel vulnerability in base64 PEM file decoding allows system-level (administrator) attackers to obtain information about se… wolfssl · wolfssl 2021-07-14 high8.1 CVE-2021-3336 DoTls13CertificateVerify in tls13.c in wolfSSL before 4.7.0 does not cease processing for certain anomalous peer behavior (sending an ED22519, ED448, ECC, or R… wolfssl · wolfssl 2021-01-29 critical9.8 CVE-2020-36177 RsaPad_PSS in wolfcrypt/src/rsa.c in wolfSSL before 4.6.0 has an out-of-bounds write for certain relationships between key size and digest size. wolfssl · wolfssl 2021-01-06 medium6.8 CVE-2020-24613 wolfSSL before 4.5.0 mishandles TLS 1.3 server data in the WAIT_CERT_CR state, within SanityCheckTls13MsgReceived() in tls13.c. wolfssl · wolfssl 2020-08-24 medium5.3 CVE-2020-24585 An issue was discovered in the DTLS handshake implementation in wolfSSL before 4.5.0. wolfssl · wolfssl 2020-08-21 high7.0 CVE-2020-15309 An issue was discovered in wolfSSL before 4.5.0, when single precision is not employed. wolfssl · wolfssl 2020-08-21 high7.5 CVE-2020-12457 An issue was discovered in wolfSSL before 4.5.0. wolfssl · wolfssl 2020-08-21 medium5.3 CVE-2020-11735 The private-key operations in ecc.c in wolfSSL before 4.4.0 do not use a constant-time modular inverse when mapping to affine coordinates, aka a "projective co… wolfssl · wolfssl 2020-06-25 high7.5 CVE-2020-11713 wolfSSL 4.3.0 has mulmod code in wc_ecc_mulmod_ex in ecc.c that does not properly resist timing side-channel attacks. wolfssl · wolfssl 2020-04-12 critical9.8 CVE-2014-2898 wolfSSL CyaSSL before 2.9.4 allows remote attackers to have unspecified impact via multiple calls to the CyaSSL_read function which triggers an out-of-bounds r… wolfssl · wolfssl 2020-01-28 critical9.8 CVE-2014-2897 The SSL 3 HMAC functionality in wolfSSL CyaSSL 2.5.0 before 2.9.4 does not check the padding length when verification fails, which allows remote attackers to h… wolfssl · wolfssl 2020-01-28 critical9.8 CVE-2014-2896 The DoAlert function in the (1) TLS and (2) DTLS implementations in wolfSSL CyaSSL before 2.9.4 allows remote attackers to have unspecified impact and vectors,… wolfssl · wolfssl 2020-01-28 medium5.3 CVE-2019-19963 An issue was discovered in wolfSSL before 4.3.0 in a non-default configuration where DSA is enabled. wolfssl · wolfssl 2019-12-25 high7.5 CVE-2019-19962 wolfSSL before 4.3.0 mishandles calls to wc_SignatureGenerateHash, leading to fault injection in RSA cryptography. wolfssl · wolfssl 2019-12-25 medium5.3 CVE-2019-19960 In wolfSSL before 4.3.0, wc_ecc_mulmod_ex does not properly resist side-channel attacks. wolfssl · wolfssl 2019-12-25 medium5.3 CVE-2019-14317 wolfSSL and wolfCrypt 4.1.0 and earlier (formerly known as CyaSSL) generate biased DSA nonces. wolfssl · wolfssl 2019-12-11 high7.5 CVE-2014-2904 wolfssl before 3.2.0 has a server certificate that is not properly authorized for server authentication. wolfssl · wolfssl 2019-11-21 high7.5 CVE-2014-2902 wolfssl before 3.2.0 does not properly authorize CA certificate for signing other certificates. wolfssl · wolfssl 2019-11-21 high7.5 CVE-2014-2901 wolfssl before 3.2.0 does not properly issue certificates for a server's hostname. wolfssl · wolfssl 2019-11-21

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.