NetSight

Security Dashboard

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

Reset
145 matching advisories · page 3 of 5Index updated just now · Subscribe · RSS
SeverityIDTitleAffectedAge
medium6.5 CVE-2024-52917 Bitcoin Core before 22.0 has a miniupnp infinite loop in which it allocates memory on the basis of random data received over the network, e.g., large M-SEARCH … bitcoin · bitcoin_core 2024-11-18 high7.5 CVE-2024-52916 Bitcoin Core before 0.15.0 allows a denial of service (OOM kill of a daemon process) via a flood of minimum difficulty headers. bitcoin · bitcoin_core 2024-11-18 high7.5 CVE-2024-52915 Bitcoin Core before 0.20.0 allows remote attackers to cause a denial of service (memory consumption) via a crafted INV message. bitcoin · bitcoin_core 2024-11-18 high7.5 CVE-2024-52914 In Bitcoin Core before 0.18.0, a node could be stalled for hours when processing the orphans of a crafted unconfirmed transaction. bitcoin · bitcoin_core 2024-11-18 medium5.3 CVE-2024-52913 In Bitcoin Core before 0.21.0, an attacker could prevent a node from seeing a specific unconfirmed transaction, because transaction re-requests are mishandled. bitcoin · bitcoin_core 2024-11-18 high7.5 CVE-2024-52912 Bitcoin Core before 0.21.0 allows a network split that is resultant from an integer overflow (calculating the time offset for newly connecting peers) and an ab… bitcoin · bitcoin_core 2024-11-18 high7.5 CVE-2019-25220 Bitcoin Core before 24.0.1 allows remote attackers to cause a denial of service (daemon crash) via a flood of low-difficulty header chains (aka a "Chain Width … bitcoin · bitcoin_core 2024-11-18 critical9.8 CVE-2015-20111 miniupnp before 4c90b87, as used in Bitcoin Core before 0.12 and other products, lacks checks for snprintf return values, leading to a buffer overflow and sign… Bitcoin Core 2024-11-18 high7.4 CVE-2024-38365 btcd did not correctly re-implement Bitcoin Core's "FindAndDelete()" functionality go · github.com/btcsuite/btcd 2024-10-10 high7.5 CVE-2024-35202 Bitcoin Core before 25.0 allows remote attackers to cause a denial of service (blocktxn message-handling assertion and node exit) by including transactions in … bitcoin · bitcoin_core 2024-10-10 critical GHSA-pm94-3h9g-gm2c Malware in bitcoin-sign-messageMalware npm · bitcoin-sign-message 2024-09-04 critical GHSA-q83r-mm9j-662f Malware in bitcoin-signMalware npm · bitcoin-sign 2024-09-04 critical GHSA-r2vf-644p-jf4f Malware in bitcoin-messageMalware npm · bitcoin-message 2024-09-04 critical GHSA-rp54-p5x3-jjjj Malware in bitcoin-address-validatorMalware npm · bitcoin-address-validator 2024-09-04 critical GHSA-9v54-pj7j-jcm2 Malware in wif-bitcoinMalware npm · wif-bitcoin 2024-09-04 high7.5 CVE-2024-44073 Miniscript allows stack consumption rust · miniscript 2024-08-19 medium6.3 CVE-2024-34149 In Bitcoin Core through 27.0 and Bitcoin Knots before 25.1.knots20231115, tapscript lacks a policy size limit check, a different issue than CVE-2023-50428. Bitcoin Core, Bitcoin Knots 2024-04-30 medium5.6 CVE-2024-0676 Weak password requirement vulnerability in Lamassu Bitcoin ATM Douro machines, in its 7.1 version , which allows a local user to interact with the machine wher… lamassu · douro_firmware, lamassu · douro_ii_firmware 2024-01-30 medium6.3 CVE-2024-0675 Vulnerability of improper checking for unusual or exceptional conditions in Lamassu Bitcoin ATM Douro machines, in its 7.1 version, the exploitation of which c… lamassu · douro_firmware, lamassu · douro_ii_firmware 2024-01-30 medium6.3 CVE-2024-0674 Privilege escalation vulnerability in Lamassu Bitcoin ATM Douro machines, in its 7.1 version, which could allow a local user to acquire root permissions by mod… lamassu · douro_firmware, lamassu · douro_ii_firmware 2024-01-30 medium5.3 CVE-2023-50428 In Bitcoin Core through 26.0 and Bitcoin Knots before 25.1.knots20231115, datacarrier size limits can be bypassed by obfuscating data as code (e.g., with OP_FA… bitcoin · bitcoin_core, bitcoinknots · bitcoin_knots 2023-12-09 medium5.3 CVE-2015-6964 MultiBit HD before 0.1.2 allows attackers to conduct bit-flipping attacks that insert unspendable Bitcoin addresses into the list that MultiBit uses to send fe… multibit · multibit_hd 2023-09-25 high7.5 CVE-2023-39910 The cryptocurrency wallet entropy seeding mechanism used in Libbitcoin Explorer 3.0.0 through 3.6.0 is weak, aka the Milk Sad issue. libbitcoin · libbitcoin_explorer 2023-08-09 high7.5 CVE-2023-37192 Memory management and protection issues in Bitcoin Core v22 allows attackers to modify the stored sending address within the app's memory, potentially allowing… bitcoin · bitcoin_core 2023-07-07 high7.5 CVE-2023-33297 Bitcoin Core before 24.1, when debug mode is not used, allows attackers to cause a denial of service (e.g., CPU consumption) because draining the inventory-to-… bitcoin · bitcoin_core 2023-05-22 critical9.8 CVE-2022-4118 The Bitcoin / AltCoin Payment Gateway for WooCommerce & Multivendor store / shop WordPress plugin through 1.7.1 does not properly sanitise and escape a paramet… coinmarketstats · bitcoin_\/_altcoin_payment_gateway_for_woocommerce 2023-05-08 high7.1 CVE-2022-47145 Reflected Cross-Site Scripting (XSS) vulnerability in Blockonomics WordPress Bitcoin Payments – Blockonomics plugin <= 3.5.7 versions. blockonomics · blockonomics 2023-03-23 medium5.4 CVE-2022-3025 The Bitcoin / Altcoin Faucet WordPress plugin through 1.6.0 does not have any CSRF check when saving its settings, allowing attacker to make a logged in admin … bitcoin\/altcoin_faucet_project · bitcoin\/altcoin_faucet 2022-09-26 medium5.4 CVE-2022-3024 The Simple Bitcoin Faucets WordPress plugin through 1.7.0 does not have any authorisation and CSRF in an AJAX action, allowing any authenticated users, such as… simple_bitcoin_faucets_project · simple_bitcoin_faucets 2022-09-26 critical GHSA-426m-pjp5-6pf6 Malware in bitcoinjs-lib-bigintMalware npm · bitcoinjs-lib-bigint 2022-06-20

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.