Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

briant2token vulnerabilities and fixes

Recent CVEs affecting briant2token, with upgrade or downgrade steps. 1 tracked.

briant2token has 1 tracked vulnerability, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2018-07-09. Highest priority: CVE-2018-13603 (score 47/100).

FAQ

How do I fix briant2token vulnerabilities?

Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.

Is briant2token being exploited right now?

None of the tracked briant2token CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.

Which briant2token CVE should I patch first?

CVE-2018-13603 currently ranks highest (47/100): The mintToken function of a smart contract implementation for Briant2Token, an Ethereum token, has an integer .

← Back to latest CVEs