Security readout for executives and security teams
Plain-English summary
CVE-2018-14084 describes an integer overflow risk in an MKCB Ethereum token smart contract. If the contract owner sets a very large sell price, the sell calculation can wrap around and produce incorrect results. The public record gives limited product and severity detail, so urgency depends on whether your organization touches this token or reused its code.
Executive priority
Treat this as a targeted exposure question, not a broad enterprise emergency. Prioritize confirmation if your organization holds, integrates, trades, or copied code from MKCB. If there is no MKCB exposure, business urgency is low despite incomplete severity scoring.
Technical view
The issue is in MKCB token contract logic: setPrices() can assign a large sellPrice, and sell() multiplies amount by sellPrice without documented overflow protection. The CVE record does not name a vendor, version, CVSS score, patch, or CWE, and only cites a public blockchain vulnerability reference.
Likely exposure
Exposure appears narrow: direct MKCB token holders, systems integrating with that token, or projects that copied the vulnerable smart contract pattern. The CVE record lists affected vendor and product as n/a, so confirm exposure from your own token, wallet, exchange, or contract inventory.
Exploitation context
CISA KEV is false, and the supplied sources do not claim active exploitation. The described condition depends on the owner setting sellPrice to a large value, causing overflow in a sell calculation. No exploit status, observed abuse, or proof-of-concept details are provided in the bundle.
Researcher notes
The record is sparse: no CVSS, CWE, vendor, versions, patch, or exploit confirmation. The core signal is unchecked multiplication in smart contract sell logic after owner-controlled sellPrice configuration. Analysis should focus on contract provenance and whether the vulnerable arithmetic exists in deployed or forked code.
Mitigation direction
- Check whether any application, treasury, wallet, or exchange flow uses MKCB.
- Review vendor or project guidance before relying on a fix assumption.
- Avoid deploying forks of the referenced contract without overflow-safe arithmetic review.
- For owned forks, require smart contract audit before production use.
- Limit business reliance on affected token flows until exposure is confirmed.
Validation and detection
- Inventory token contracts and integrations for MKCB references.
- Check copied contract code for setPrices(), sellPrice, and sell() arithmetic.
- Confirm whether arithmetic overflow protection is present in any forked implementation.
- Review internal transaction exposure involving MKCB token flows.
- Document findings because public affected-version data is incomplete.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
Credential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2018-14084 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/hellowuzekai/blockchains/blob/master/README.mdCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.