CVE-2018-14084: An issue was discovered in a smart contract implementation for MKCB, an Ethereum token
CVE-2018-14084 is a critical-severity flaw (CVSS 9.8) affecting myadvancedtoken. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
An issue was discovered in a smart contract implementation for MKCB, an Ethereum token. If the owner sets the value of sellPrice to a large number in setPrices() then the "amount * sellPrice" will cause an integer overflow in sell().
Why this priority
- Critical severity
- Public exploit reference
- Remotely exploitable, no login, no user action
No fix is published yet: follow the downgrade or mitigation steps.
Risk facts
| CVSS score | 9.8 (Critical) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 1.2% (top 31%) |
| CISA exploited list | No |
| Weakness | CWE-190 |
| Published | 2018-07-16 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2018-14084?
myadvancedtoken: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2018-14084 being exploited?
CVE-2018-14084 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2018-14084 affect?
CVE-2018-14084 affects myadvancedtoken. Severity is critical (CVSS 9.8). An issue was discovered in a smart contract implementation for MKCB, an Ethereum token. If the owner sets the value of sellPrice to a large number in setPrices() then the "amount * sellPrice" will cause an integer overflow in sell().
How urgent is CVE-2018-14084?
Priority 62/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action