NetSight

Security Dashboard

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

Reset
560 matching advisories · page 2 of 19Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
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 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 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 high8.7 CVE-2020-5232 Malicious takeover of previously owned ENS names npm · @ensdomains/ens 2020-01-30 high7.5 CVE-2018-19834 The quaker function of a smart contract implementation for BOMBBA (BOMB), an tradable Ethereum ERC20 token, allows attackers to change the owner of the contrac… bombba_project · bombba 2019-12-31 high7.5 CVE-2018-19833 The owned function of a smart contract implementation for DDQ, an tradable Ethereum ERC20 token, allows attackers to change the owner of the contract, because … ddq_project · ddq 2019-12-31 high7.5 CVE-2018-19832 The NETM() function of a smart contract implementation for NewIntelTechMedia (NETM), an tradable Ethereum ERC20 token, allows attackers to change the owner of … newinteltechmedia_project · newinteltechmedia 2019-12-31 high7.5 CVE-2018-19831 The ToOwner() function of a smart contract implementation for Cryptbond Network (CBN), an tradable Ethereum ERC20 token, allows attackers to change the owner o… cryptbond_network_project · cryptbond_network 2019-12-31 high7.5 CVE-2018-19830 The UBSexToken() function of a smart contract implementation for Business Alliance Financial Circle (BAFC), an tradable Ethereum ERC20 token, allows attackers … business_alliance_financial_circle_project · business_alliance_financial_circle 2019-12-31 high7.5 CVE-2018-17882 An Integer overflow vulnerability exists in the batchTransfer function of a smart contract implementation for CryptoBotsBattle (CBTB), an Ethereum token. cryptobots · battletoken 2019-03-15 high7.5 CVE-2018-18667 The mintToken function of Pylon (PYLNT) aka PylonToken, an Ethereum token, has an integer overflow that allows the owner of the contract to set the balance of … pylon-network · pylontoken 2018-12-28 high7.5 CVE-2018-18666 The mintToken function of SwftCoin (SWFTC) aka SwftCoin, an Ethereum token, has an integer overflow that allows the owner of the contract to set the balance of… swft · swftcoin 2018-12-28 high7.5 CVE-2018-18665 The mintToken function of Nexxus (NXX) aka NexxusToken, an Ethereum token, has an integer overflow that allows the owner of the contract to set the balance of … nexxuscoin · nexxustoken 2018-12-28 high7.5 CVE-2018-17987 The determineWinner function of a smart contract implementation for HashHeroes Tiles, an Ethereum game, uses a certain blockhash value in an attempt to generat… hashheroes · hashheroes 2018-12-26 high7.5 CVE-2018-20421 Go Ethereum (aka geth) 1.8.19 allows attackers to cause a denial of service (memory consumption) by rewriting the length of a dynamic array in memory, and then… ethereum · go_ethereum 2018-12-24 high7.5 CVE-2018-19184 Go Ethereum Denial of Service go · github.com/ethereum/go-ethereum 2018-11-12 high7.5 CVE-2018-19183 Denial of Service in ethereumjs-vm npm · ethereumjs-vm 2018-11-12 high8.8 CVE-2018-18920 Py-EVM is vulnerable to arbitrary bytecode injection pip · py-evm 2018-11-12 high7.5 CVE-2018-17968 A gambling smart contract implementation for RuletkaIo, an Ethereum gambling game, generates a random value that is predictable by an external contract call. ruletkaio · ruletkaio 2018-10-23 high7.5 CVE-2018-17877 A lottery smart contract implementation for Greedy 599, an Ethereum gambling game, generates a random value that is predictable via an external contract call. greedy599 · greedy_599 2018-10-23 high7.5 CVE-2018-12975 The random() function of the smart contract implementation for CryptoSaga, an Ethereum game, generates a random value with publicly readable variables such as … cryptosaga · cryptosaga 2018-09-24 high7.5 CVE-2018-17050 The mintToken function of a smart contract implementation for PolyAi (AI), an Ethereum token, has an integer overflow that allows the owner of the contract to … polyai_project · polyai 2018-09-21 high7.5 CVE-2018-12511 In the mintToken function of a smart contract implementation for Substratum (SUB), an Ethereum ERC20 token, the administrator can control mintedAmount, leverag… substratum · substratum 2018-09-21 high7.5 CVE-2018-17071 The fallback function of a simple lottery smart contract implementation for Lucky9io, an Ethereum gambling game, generates a random value with the publicly rea… lucky9 · lucky9io 2018-09-18 high7.5 CVE-2018-16733 Go Ethereum Improper Input Validation go · github.com/ethereum/go-ethereum 2018-09-08

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.