NetSight

Security Dashboard

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

Reset
664 matching advisories · page 4 of 23Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.5 CVE-2022-23327 Denial of Service in Go-Ethereum go · github.com/ethereum/go-ethereum 2022-03-04 high7.5 CVE-2021-41272 Besu is an Ethereum client written in Java. linuxfoundation · besu 2021-12-13 medium5.5 CVE-2021-43668 Denial of Service in Go-Ethereum go · github.com/ethereum/go-ethereum 2021-11-18 medium5.7 CVE-2021-41173 Go Ethereum is the official Golang implementation of the Ethereum protocol. go · github.com/ethereum/go-ethereum 2021-10-25 critical9.1 CVE-2021-42766 The Proof-of-Stake (PoS) Ethereum consensus protocol through 2021-10-19 allows an adversary to cause a denial of service (long-range consensus chain reorganiza… proof-of-stake_ethereum_project · proof-of-stake_ethereum 2021-10-20 high7.5 CVE-2021-42765 The Proof-of-Stake (PoS) Ethereum consensus protocol through 2021-10-19 allows an adversary to leverage network delay to cause a denial of service (indefinite … proof-of-stake_ethereum_project · proof-of-stake_ethereum 2021-10-20 critical9.1 CVE-2021-42764 The Proof-of-Stake (PoS) Ethereum consensus protocol through 2021-10-19 allows an adversary to cause a denial of service (delayed consensus decisions), and als… proof-of-stake_ethereum_project · proof-of-stake_ethereum 2021-10-20 medium5.3 CVE-2021-41138 Validity check missing in Frontier rust · pallet-ethereum 2021-10-13 high7.5 CVE-2020-19765 An issue in the noReentrance() modifier of the Ethereum-based contract Accounting 1.0 allows attackers to carry out a reentrancy attack. proofofdiligencetoken_project · proofofdiligencetoken 2021-09-07 medium5.3 CVE-2021-39193 Transaction validity oversight in pallet-ethereum rust · pallet-ethereum 2021-09-01 medium6.5 CVE-2021-39137 go-ethereum is the official Go implementation of the Ethereum protocol. go · github.com/ethereum/go-ethereum 2021-08-24 high7.5 CVE-2021-34273 A security flaw in the 'owned' function of a smart contract implementation for BTC2X (B2X), a tradeable Ethereum ERC20 token, allows attackers to hijack victim… b2x_project · b2x 2021-08-03 high7.5 CVE-2021-34272 A security flaw in the 'owned' function of a smart contract implementation for RobotCoin (RBTC), a tradeable Ethereum ERC20 token, allows attackers to hijack v… robotbtc_project · robotbtc 2021-08-03 high7.5 CVE-2021-34270 An integer overflow in the mintToken function of a smart contract implementation for Doftcoin Token, an Ethereum ERC20 token, allows the owner to cause unexpec… doft · doftcoin 2021-08-03 high7.5 CVE-2021-33403 An integer overflow in the transfer function of a smart contract implementation for Lancer Token, an Ethereum ERC20 token, allows the owner to cause unexpected… blocklancertoken_project · blocklancertoken 2021-08-03 critical GHSA-m6gx-rhvj-fh52 Denial of service in go-ethereum due to CVE-2020-28362 go · github.com/ethereum/go-ethereum 2021-06-29 medium6.5 CVE-2020-17753 An issue was discovered in function addMeByRC in the smart contract implementation for RC, an Ethereum token, allows attackers to transfer an arbitrary amount … rc_project · rc, rcpro_project · rcpro 2021-06-24 critical9.8 CVE-2020-17752 Integer overflow vulnerability in payable function of a smart contract implementation for an Ethereum token, as demonstrated by the smart contract implemented … mon_project · mon 2021-06-24 high7.5 CVE-2020-20178 Ethereum 0xe933c0cd9784414d5f278c114904f5a84b396919#code.sol latest version is affected by a denial of service vulnerability in the affected payout function. whohas_project · whohas 2021-05-24 medium6.5 CVE-2021-21369 Hyperledger Besu is an open-source, MainNet compatible, Ethereum client written in Java. linuxfoundation · besu 2021-03-09 medium5.5 CVE-2020-26800 A stack overflow vulnerability in Aleth Ethereum C++ client version <= 1.8.0 using a specially crafted a config.json file may result in a denial of service. ethereum · aleth 2021-01-11 high7.5 CVE-2020-35962 The sellTokenForLRC function in the vault protocol in the smart contract implementation for Loopring (LRC), an Ethereum token, lacks access control for fee swa… loopring · loopring 2021-01-03 high7.5 CVE-2021-3006 The breed function in the smart contract implementation for Farm in Seal Finance (Seal), an Ethereum token, lacks access control and thus allows price manipula… seal_finance_project · seal_finance 2021-01-03 high7.5 CVE-2021-3004 The _deposit function in the smart contract implementation for Stable Yield Credit (yCREDIT), an Ethereum token, has certain incorrect calculations. stableyieldcredit_project · stableyieldcredit 2021-01-03 high7.5 CVE-2019-15080 An issue was discovered in a smart contract implementation for MORPH Token through 2019-06-05, an Ethereum token. morph_project · morph 2020-12-30 high7.5 CVE-2019-15079 A typo exists in the constructor of a smart contract implementation for EAI through 2019-06-05, an Ethereum token. eai_project · eai 2020-12-30 high7.5 CVE-2019-15078 An issue was discovered in a smart contract implementation for AIRDROPX BORN through 2019-05-29, an Ethereum token. xbornid · xbornid 2020-12-30 medium5.3 CVE-2020-26265 Go Ethereum, or "Geth", is the official Golang implementation of the Ethereum protocol. go · github.com/ethereum/go-ethereum 2020-12-11 medium6.5 CVE-2020-26264 Go Ethereum, or "Geth", is the official Golang implementation of the Ethereum protocol. go · github.com/ethereum/go-ethereum 2020-12-11 critical10.0 CVE-2017-14451 An exploitable out-of-bounds read vulnerability exists in libevm (Ethereum Virtual Machine) of CPP-Ethereum. ethereum · ethereum 2020-12-02

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.