Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

my2token vulnerabilities and fixes

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

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

FAQ

How do I fix my2token 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 my2token being exploited right now?

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

Which my2token CVE should I patch first?

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

← Back to latest CVEs