NetSight

Security Dashboard

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

Reset
664 matching advisories · page 20 of 23Index updated 2 minutes ago · Subscribe · RSS
SeverityIDTitleAffectedAge
high7.5 CVE-2018-13162 The mintToken function of a smart contract implementation for ALEX, an Ethereum token, has an integer overflow that allows the owner of the contract to set the… alex_project · alex 2018-07-05 high7.5 CVE-2018-13161 The mintToken function of a smart contract implementation for MultiGames (MLT), an Ethereum token, has an integer overflow that allows the owner of the contrac… multigames_project · multigames 2018-07-05 high7.5 CVE-2018-13160 The mintToken function of a smart contract implementation for etktokens (ETK), an Ethereum token, has an integer overflow that allows the owner of the contract… etktokens_project · etktokens 2018-07-05 high7.5 CVE-2018-13159 The mintToken function of a smart contract implementation for bankcoin (BNK), an Ethereum token, has an integer overflow that allows the owner of the contract … bankcoin_project · bankcoin 2018-07-05 high7.5 CVE-2018-13158 The mintToken function of a smart contract implementation for AssetToken, an Ethereum token, has an integer overflow that allows the owner of the contract to s… assettoken_project · assettoken 2018-07-05 high7.5 CVE-2018-13157 The mintToken function of a smart contract implementation for CryptonitexCoin, an Ethereum token, has an integer overflow that allows the owner of the contract… cryptonitexcoin_project · cryptonitexcoin 2018-07-05 high7.5 CVE-2018-13156 The mintToken function of a smart contract implementation for bonusToken (BNS), an Ethereum token, has an integer overflow that allows the owner of the contrac… bonustoken_project · bonustoken 2018-07-05 high7.5 CVE-2018-13155 The mintToken function of a smart contract implementation for GEMCHAIN (GEM), an Ethereum token, has an integer overflow that allows the owner of the contract … gemchain_project · gemchain 2018-07-05 high7.5 CVE-2018-12018 Go Ethereum LES protocol implementation vulnerable to Denial of Service go · github.com/ethereum/go-ethereum 2018-07-05 high7.5 CVE-2018-13146 The mintToken, buy, and sell functions of a smart contract implementation for LEF, an Ethereum token, have an integer overflow. lef_project · lef 2018-07-04 high7.5 CVE-2018-13145 The mintToken function of a smart contract implementation for JavaSwapTest (JST), an Ethereum token, has an integer overflow. javaswaptest_project · javaswaptest 2018-07-04 high7.5 CVE-2018-13144 The transfer and transferFrom functions of a smart contract implementation for Pandora (PDX), an Ethereum token, have an integer overflow. pandora_project · pandora 2018-07-04 high7.5 CVE-2018-13132 Spadeico is a smart contract running on Ethereum. spadeico_project · spadeico 2018-07-04 high7.5 CVE-2018-13131 SpadePreSale is a smart contract running on Ethereum. spadepresale_project · spadepresale 2018-07-04 high7.5 CVE-2018-13130 Bitotal (TFUND) is a smart contract running on Ethereum. bitotal · bitotal 2018-07-04 high7.5 CVE-2018-13129 SP8DE Token (SPX) is a smart contract running on Ethereum. sp8de · sp8de 2018-07-04 high7.5 CVE-2018-13128 Etherty Token (ETY) is a smart contract running on Ethereum. etherty · etherty_token 2018-07-04 high7.5 CVE-2018-13127 SP8DE PreSale Token (DSPX) is a smart contract running on Ethereum. sp8de · sp8de_presale_token 2018-07-04 high7.5 CVE-2018-13126 MoxyOnePresale is a smart contract running on Ethereum. moxy · moxyonepresale 2018-07-04 high7.5 CVE-2018-11429 ATLANT (ATL) is a smart contract running on Ethereum. atlant · atlant 2018-07-04 high7.5 CVE-2018-11335 GVToken Genesis Vision (GVT) is a smart contract running on Ethereum. genesis_vision · gvtoken 2018-07-04 high7.5 CVE-2018-13113 The transfer and transferFrom functions of a smart contract implementation for Easy Trading Token (ETT), an Ethereum token, have an integer overflow. easy_trading_token_project · easy_trading_token 2018-07-03 high7.5 CVE-2018-13092 The mintToken function of a smart contract implementation for Reimburse Token (REIM), an Ethereum token, has an integer overflow that allows the owner of the c… reimbursetoken_project · reimbursetoken 2018-07-03 high7.5 CVE-2018-13091 The mintToken function of a smart contract implementation for sumocoin (SUMO), an Ethereum token, has an integer overflow that allows the owner of the contract… sumocoin_project · sumocoin 2018-07-03 high7.5 CVE-2018-13090 The mintToken function of a smart contract implementation for YiTongCoin (YTC), an Ethereum token, has an integer overflow that allows the owner of the contrac… yitongcoin_project · yitongcoin 2018-07-03 high7.5 CVE-2018-13089 The mintToken function of a smart contract implementation for Universal Coin (UCOIN), an Ethereum token, has an integer overflow that allows the owner of the c… ucointoken_project · ucointoken 2018-07-03 high7.5 CVE-2018-13088 The mintToken function of a smart contract implementation for Futures Pease (FP), an Ethereum token, has an integer overflow that allows the owner of the contr… tokenerc20_project · tokenerc20 2018-07-03 high7.5 CVE-2018-13087 The mintToken function of a smart contract implementation for Coinstar (CSTR), an Ethereum token, has an integer overflow that allows the owner of the contract… coinstar_myadvancedtoken_project · coinstar_myadvancedtoken 2018-07-03 high7.5 CVE-2018-13086 The mintToken function of a smart contract implementation for IADOWR Coin (IAD), an Ethereum token, has an integer overflow that allows the owner of the contra… iadowr_project · iadowr 2018-07-03 high7.5 CVE-2018-13085 The mintToken function of a smart contract implementation for FreeCoin (FREE), an Ethereum token, has an integer overflow that allows the owner of the contract… freecoin_project · freecoin 2018-07-03

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.