NetSight

Security Dashboard

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

Reset
145 matching advisories · page 4 of 5Index updated 14 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
critical GHSA-f77c-x63w-6w5q Malware in bitcoin-json-rpc-adapterMalware npm · bitcoin-json-rpc-adapter 2022-06-20 medium6.1 CVE-2021-24679 The Bitcoin / AltCoin Payment Gateway for WooCommerce WordPress plugin before 1.6.1 does not escape the 's' GET parameter before outputting back in the All Mas… coinmarketstats · bitcoin_\/_altcoin_payment_gateway_for_woocommerce 2021-10-04 medium6.5 CVE-2021-31876 Bitcoin Core 0.12.0 through 0.21.1 does not properly implement the replacement policy specified in BIP125, which makes it easier for attackers to trigger a los… bitcoin · bitcoin 2021-05-13 critical9.8 CVE-2021-3401 Bitcoin Core before 0.19.0 might allow remote attackers to execute arbitrary code when another application unsafely passes the -platformpluginpath argument to … bitcoin · bitcoin 2021-02-04 high7.5 CVE-2021-3195 bitcoind in Bitcoin Core through 0.21.0 can create a new file in an arbitrary directory (e.g., outside the ~/.bitcoin directory) via a dumpwallet RPC call. bitcoin · bitcoin_core 2021-01-26 high7.5 CVE-2018-1000893 Bitcoin SV before 0.1.1 allows uncontrolled resource consumption when deserializing transactions. bitcoinsv · bitcoin_sv 2020-12-23 high7.5 CVE-2018-1000892 Bitcoin SV before 0.1.1 allows uncontrolled resource consumption when receiving sendheaders messages. bitcoinsv · bitcoin_sv 2020-12-23 high7.5 CVE-2018-1000891 Bitcoin SV before 0.1.1 allows uncontrolled resource consumption when receiving messages with invalid checksums. bitcoinsv · bitcoin_sv 2020-12-23 high7.5 CVE-2020-14198 Bitcoin Core 0.20.0 allows remote denial of service. bitcoin · bitcoin_core 2020-09-10 high7.5 CVE-2018-17145 Bitcoin Inventory Out-of-Memory Denial-of-Service Attack (CVE-2018-17145) npm · bcoin 2020-09-10 critical9.1 GHSA-8hqw-qp6r-vqcm Malicious Package in bitcoin-sweep npm · bitcoin-sweep 2020-09-04 critical9.1 GHSA-v8g7-9qv2-j865 Malicious Package in bitcoin-osp npm · bitcoin-osp 2020-09-04 high8.1 CVE-2020-12119 Ledger Live before 2.7.0 does not handle Bitcoin's Replace-By-Fee (RBF). ledger · ledger_live 2020-07-02 medium6.5 CVE-2020-14199 BIP-143 in the Bitcoin protocol specification mishandles the signing of a Segwit transaction, which allows attackers to trick a user into making two signatures… satoshilabs · trezor_model_t_firmware, satoshilabs · trezor_one_firmware 2020-06-16 medium6.1 CVE-2020-11944 Abe (aka bitcoin-abe) through 0.7.2, and 0.8pre, allows XSS in __call__ in abe.py because the PATH_INFO environment variable is mishandled during a PageNotFoun… bitcoin-abe_project · bitcoin-abe 2020-04-20 high7.5 CVE-2017-12842 Bitcoin Core before 0.14 allows an attacker to create an ostensibly valid SPV proof for a payment to a victim who uses an SPV wallet, even if that payment did … bitcoin · bitcoin_core 2020-03-16 medium5.3 CVE-2018-20586 bitcoind and Bitcoin-Qt prior to 0.17.1 allow injection of arbitrary data into the debug log via an RPC call. bitcoin · bitcoin_core 2020-03-12 medium5.9 CVE-2017-18350 bitcoind and Bitcoin-Qt prior to 0.15.1 have a stack-based buffer overflow if an attacker-controlled SOCKS proxy server is used. bitcoin · bitcoin_core 2020-03-12 high7.5 CVE-2015-3641 bitcoind and Bitcoin-Qt prior to 0.10.2 allow attackers to cause a denial of service (disabled functionality such as a client application crash) via an "Easy" … bitcoin · bitcoin_core 2020-03-12 high7.5 CVE-2019-15947 In Bitcoin Core 0.18.0, bitcoin-qt stores wallet.dat data unencrypted in memory. bitcoin · bitcoin_core 2019-09-05 critical9.8 CVE-2019-15224 rest-client Gem Contains Malicious Code rubygems · rest-client, rubygems · cron_parser, rubygems · coin_base +7 2019-08-19 medium5.5 CVE-2018-20587 Bitcoin Core 0.12.0 through 0.17.1 and Bitcoin Knots 0.12.0 through 0.17.x before 0.17.1.knots20181229 have Incorrect Access Control. bitcoin · bitcoin_core, bitcoinknots · bitcoin_knots 2019-02-11 critical9.8 CVE-2018-1000851 Copay Bitcoin Wallet version 5.01 to 5.1.0 included. copay · copay_bitcoin_wallet 2018-12-20 high7.5 CVE-2018-17144 Bitcoin Core 0.14.x before 0.14.3, 0.15.x before 0.15.2, and 0.16.x before 0.16.3 and Bitcoin Knots 0.14.x through 0.16.x before 0.16.3 allow a remote denial o… bitcoin · bitcoin_core, bitcoinknots · bitcoin_knots 2018-09-19 high7.5 CVE-2018-11687 An integer overflow in the distributeBTR function of a smart contract implementation for Bitcoin Red (BTCR), an Ethereum ERC20 token, allows the owner to accom… bitcoin_red_project · bitcoin_red 2018-08-15 high7.5 CVE-2018-13485 The mintToken function of a smart contract implementation for BitcoinAgileToken, an Ethereum token, has an integer overflow that allows the owner of the contra… bitcoinagile_project · bitcoinagile 2018-07-09 high7.5 CVE-2016-10725 In Bitcoin Core before v0.13.0, a non-final alert is able to block the special "final alert" (which is supposed to override all other alerts) because operation… bitcoin · bitcoin_core, bitcoin · bitcoin-qt, bitcoin · bitcoind 2018-07-05 high7.5 CVE-2016-10724 Bitcoin Core before v0.13.0 allows denial of service (memory exhaustion) triggered by the remote network alert system (deprecated since Q1 2016) if an attacker… bitcoin · bitcoin_core, bitcoin · bitcoin-qt, bitcoin · bitcoind 2018-07-05 medium4.1 CVE-2018-10812 The Bitpie application through 3.2.4 for Android and iOS uses cleartext storage for digital currency initial keys, which allows local users to steal currency b… bitpie · bitcoin_wallet 2018-05-08 medium5.4 CVE-2018-6862 Cross Site Scripting (XSS) exists in PHP Scripts Mall Bitcoin MLM Software 1.0.2 via a profile field. bitcoin_mlm_project · bitcoin_mlm 2018-02-12

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.